diff options
| author | emilylange <git@emilylange.de> | 2024-08-17 21:07:23 +0200 |
|---|---|---|
| committer | emilylange <git@emilylange.de> | 2024-08-17 21:07:23 +0200 |
| commit | 07641a91c96ddb9030ac13d62e3a3e0bb1495842 (patch) | |
| tree | 4b5d441133ecb8b4f695a4ac83f66f974c3d0881 /pkgs/development/python-modules/rangehttpserver | |
| parent | d8c8d5c8472d830f3ad689d98c5e923561834287 (diff) | |
forgejo,forgejo-lts: remove PAM support
https://forgejo.org/docs/latest/user/authentication/#pam-pluggable-authentication-module
PAM support has to be enabled at compile time and upstream considers it
opt-in.
Official upstream binaries have it disabled.
We enabled it by default because we simply inherited most of it from
Gitea when the split in nixpkgs happened.
Reasons why it had been enabled in nixpkgs for Gitea are unknown.
See 9406f240a7b5ed68e8e633b8c764cfd69c470696.
There is reason to believe not a single Forgejo instance running on
NixOS uses this feature because it literally segfaults due to our
sandboxing.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
