If there are specific configurations that are not currently supported by
pam-auth-update that you believe should be, please file a bug against
the relevant pam module package requesting that they be supported.
But beyond that, yes, full configuration of the PAM stack *is* arcane
magic, which is why pam-auth-update does not expose it. It's
unrealistic to think that a GUI tool can expose this full functionality
and be any more usable than direct editing of the config files, *and* it
would be more error-prone because of the added abstraction layer. The
pam-auth-update "profile" approach provides a reasonable compromise
between flexibility and ease-of-use; I don't intend to expose more than
this at the GUI level.
As for your comparison with gufw and ufw, if your meaning here is that
there should be a GUI frontend to pam-auth-update, there's no need -
pam-auth-update already uses the standard debconf interface, which means
that by default on Ubuntu desktops it will use the GNOME frontend.
** Changed in: pam (Ubuntu)
Status: New => Invalid
--
PAM configuration prone to mis-configuration
https://bugs.launchpad.net/bugs/277667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
