🔒Radicle Vulnerabilities Expose Private Repositories
Your private repos are at risk, Radicle users
TL;DR
Two critical security flaws in Radicle's network protocol expose private repositories to unauthorized access. Encryption in transit is crucial for private repos until a fix is released.
Two critical security vulnerabilities in Radicle's network protocol have been reported, affecting all versions released to date. The main concern is information leakage, with network traffic between nodes not encrypted or authenticated. For private repositories, encryption in transit is crucial to prevent unauthorized access. A fix is being developed, but it will be a breaking change, requiring a major version bump. The resolution involves replacing Radicle's networking protocol with iroh, an open-source peer-to-peer networking stack. Until then, users should stop seeding private repositories and consider additional encrypted transports or waiting for the security update.

Key Points
Two critical security vulnerabilities in Radicle's network protocol affect all versions released to date.
Keep reading — it's free
Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.
Already a member? Sign in
Comments
Be the first to comment