[Bug 965662] Re: pam-auth-update conflict resolution shouldn't warn

[Steve Langasek]

On Mon, Mar 26, 2012 at 09:40:47PM -0000, Ray Link wrote:
> Then why does pam-auth-update deactivate only the lower priority module
> when a Conflict: is found?

Because in a corner case when using the noninteractive frontend,
deactivating both could mean there are no modules enabled, resulting in all
users being locked out of the system.  So given that we need to leave at
least one module enabled, priority is as good a method of selecting between
them as any.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/965662

Title:
  pam-auth-update conflict resolution shouldn't warn

Status in “pam” package in Ubuntu:
  Invalid

Bug description:
  After automatically resolving conflicts in pam-config stubs, pam-auth-
  update will still pop up a warning notification that requires the user
  to select [Ok].

  Requiring user interaction kind of defeats the purpose of having the
  automatic Conflicts and Priority conflict-resolution mechanism, and
  the priority-"high" warning box for presenting non-essential
  information is itself arguably a policy violation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/965662/+subscriptions