Quoting Borden (2026-09-20 09:26:41) > > > > Debian package python3-pam is incompatible with radicale. This is > > considered an upstream issue of low importance: directly accessing PAM > > is discouraged, safer methods exist, including a tested, packaged and > > documented method via apache2 authnz-external module. > > > No dispute. Judging from the activity on this bug, I'm probably the only > person whom this will ever affect, so you can probaly close under "user > educated."
I can imagine others than you and me running into this issue. Yes, I can imagine not only me and you but everyone else reading this bugreport coming to the conclusion that they choose not to take on the task of pushing the contained patch upstream - i.e. effectively this bugreport being stalled. But even then I don't see that as a failure: It still exists as a place of detailed documentation about the issue. In fact, I wrote the above summary as the first sentence of my previous post *exactly* because I think this bugreport might be helpful in the future: Afterwards I tagged that post as the current "summary" of this bugreport, which causes the bugreport web page to include that first paragraph in the structured top section. > > Debian radicale package does not imply that it works with PAM. > > > All I can say is that it wasn't obvious to me that it _wouldn't_ work until I > did some research. Maybe the package readme file was the place to start, but > "Do not use on Debian" was not in my top search results. I try to make a good > faith effort to exhaust my options before contacting a human, so that helped > me find this bug reports. Currently the the package descriptions for radicale and radicale-uwsgi mentions "PAM", the README.Debian for radicale documents the recommended way to enable PAM authentication, and README.Debian for python3-radicale mentions explicitly the discouraged way to enable PAM, referncing this bugreport. > > In short: Please engage upstream to have them enable support for the > > PAM module in Debian, e.g. using the patch attached to this bugreport. > > > Someone else can take up that cross, especially considering how my bug > reports get received. I saw the configuration option and thought "Wonder if I > can do it?" I don't really remember how or when I figured out that I wasn't > supposed to use it. That means I also can't remember what would have to > change to learn this earlier in my troubleshooting process. > > I hope something here was useful. I certainly appreciate the conversation we've had here, regardless of my not choosing to take on the work or doing the changes that you had envisioned. I sure hope you are not discouraged from bringing up other issues you come across in the future - here or elsewhere. - 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
