Radicle: Disclosure of Vulnerability in the Network Protocol

>This was reported to us by Konstantinos Maninakis on 2026-06-24.

announcement 3 months later is not super great, considering that the current advice is "Stop using private repositories (over the network) until the security update is released."

▲

Velocifyer 36 minutes ago | parent | prev | next [-]

My main wish is if radicle had a way to make issues online, without installing the software. Runing a piece of software is a high barrier of entry to make a bug report, which the entire reason I use codeberg instead.

	▲	someonebaggy 10 minutes ago \| parent [-]
		That's a downside of all decentralised software, isn't it? If there's a convenient access point, that access point is also a point of centralisation. To be distributed, you have to be running the software yourself. The big problem is that the software always ends up being inconvenient. People have no problem using bittorrent because the software is actually usable.

▲

ewy1 12 minutes ago | parent | prev | next [-]

thankfully (for me), this is about the git forge and not the oss calendar and contact synchronization software by the same name

https://radicale.org/v3.html

	▲	kamranjon 10 minutes ago \| parent [-]
		it's not the same name

▲

Tiberium an hour ago | parent | prev [-]

I honestly thought there would be some elaborate chain there, not "we forgot to use encryption"...

	▲	pixl97 41 minutes ago \| parent [-]
		Honestly issues like this crop up pretty commonly. JWT alg:none for example. Or even older people forcing SSL to downgrade to encryption null. In any system that provides security it should only be designed to run if the security is in use, and to fail immediately with no further action if the security is not used.