Package: radicale Version: 3.0.6-3 Severity: important Has been reported upstream: https://github.com/Kozea/Radicale/issues/1183
Upstream has been completely unresponsive. No fix is available. Their changelog fails to mentions any fix for this. Reputedly upstream plans to force upgrades and doing so would violate Debian policy. With no fix available this renders the Radicale package useless unless one wishes to run in with an insecure configuration (disable TLS/SSL). Sorry to say this, but perhaps the Radicale package needs to be removed from Debian if this is the support level. Clients known effected include iPhone and DAVx5 (Android). I suspect this only manifests if Radicale is in the standalone configuration (likely not when setup as an Apache module). Presently the only visible solution is to remain with the old stable version of Radicale. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
