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 is no facility for disabling them (until noble, which introduces the --disable flag), short of editing the profile's Default setting.
Given this is "working as designed", I'm setting this to invalid status. A case might be made to backport the "--disable" functionality from noble, but new functionality in stable releases has a high bar to pass SRU policy (https://canonical-sru-docs.readthedocs- hosted.com/en/latest/reference/requirements/#requirements). ** Changed in: pam (Ubuntu) Status: New => Invalid -- 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.launchpad.net/ubuntu/+source/pam/+bug/2089712/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
