Hi Borden, Quoting Borden (2026-03-14 01:49:28) > I'm all for dropping features for whatever reason. I suggest three things: > > 1) Remove the option from /etc/radicale/config, so people don't think they > can enable it. > 2) Comment in the readme that PAM won't work for the reasons you provided. > This will stop people from relying on the upstream documentation or other > tutorials online (which say it should just work).3) Change the error message > to journald when radicale is started with PAM enabled, which currently reads > "An exception occurred during server startup: PAM authentication requires the > Python pam module", implying that PAM authentication will work with the right > packages. This is what I thought until I found this bug report. It should > probably say "PAM authentication is not supported" instead. > The benefit to you is that fewer people like me will bother you trying to > understand why it's not working (if they don't stumble upon this bug first). > I'm not sure whether an undocumented feature worse than a documented > unfeature.
Thanks for your attempt at concrete actions that could be taken. As I wrote in my 1st reply, I will not get in the way of people wanting to setup a lighter but also less secure system, so I will not remove options. It seems I am therefore not convinced that 1) is a good idea, but please do try be even more specific, if you think that some concrete edits would be sensible without hiding options for more adventurous users. Same for 2): Can you suggest concrete changes to the documentation? That would help me reflect on whether I find that an improvement over the existing texts, and something that I feel that I am ok maintaining. Thanks, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
