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-runtime 1.5.3-5ubuntu5.1
all Runtime support for the PAM library
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2089712
Title:
pam-auth-update --remove doesn't work properly
Status in pam package in Ubuntu:
New
Bug description:
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.
OS: jammy
libpam-runtime: 1.4.0-11ubuntu2.4
The profile I use
```
cat << EOF > /usr/share/pam-configs/faillock
Name: Notify of failed login attempts and reset count upon success
Default: yes
Priority: 1024
Auth-Type: Primary
Auth:
requisite pam_faillock.so preauth
Account-Type: Primary
Account:
required pam_faillock.so
EOF
cat << EOF > /usr/share/pam-configs/faillock_notify
Name: Notify of failed login attempts and reset count upon success
Default: yes
Priority: 1024
Auth-Type: Primary
Auth:
requisite pam_faillock.so preauth
Account-Type: Primary
Account:
required pam_faillock.so
EOF
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2089712/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
