This does appear to be "working as designed" on jammy.
Tested with the profiles in the original report and as noted in comment
2, whilst pam-auth-update --remove will transiently disable the profiles
in the PAM configuration, any subsequent run of pam-auth-update will re-
enable them because there
** Description changed:
Issue:
- If use `pam-auth-update --remove profile` to remove a profile, it has no
effect: the /etc/pam.d/common-auth doesn't change at all.
+ If use `pam-auth-update --remove profile` to remove a profile, it has no
effect: the /etc/pam.d/common-auth doesn't change at a
The --disable flag does not exist in Jammy, it was introduced in PAM
1.5.2-6 https://tracker.debian.org/news/1405352/accepted-
pam-152-6-source-into-unstable/
The two files are the same which is probably not intended as they will add the
same entries twice.
Using the below config, `pam auth-upda
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089712
Title:
pam-auth-update --remove doesn't work properly
To manage notifications about this bug go to:
https://bugs
Tested on noble vm too. The `pam-auth-update --disable faillock
faillock_notify && pam-auth-update --remove faillock faillock_notify`
work perfectly fine
OS: noble
dpkg -l | grep libpam-runtime
ii libpam-runtime1.5.3-5ubuntu5.1
all
