Radicle tells users to stop using private repositories over its network
Radicle says every released version is affected; a fix requires a breaking major upgrade that will split upgraded nodes from the old network.
By RuntimeWire Staff · Published
Primary source: Radicle
Why it matters
Radicle's security warning shows how a peer-to-peer code forge can preserve repository integrity while still exposing private data at the transport layer. Its fix requires a major protocol upgrade that will divide nodes that upgrade from those that do not.
Radicle told users on September 23rd to stop using private repositories over its peer-to-peer network after disclosing two vulnerabilities affecting every released version. The notice puts the project founded by Eleftherios Diakomichalis and Alexis Sellier in a difficult position: the network was built to let developers collaborate without a central host, yet its current transport can expose private code to people watching connections between nodes.…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.