Thank you for taking the time to report this issue and help to improve
Ubuntu.
In addition to the 'use_authtok' solution, which is recommended
generally, the specific problem you reported has been resolved as of pam
1.0.1-6:
pam (1.0.1-6) unstable; urgency=low
* Updated debconf translations:
- Vietnamese, thanks to Clytie Siddall <[email protected]>
* New patch dont_freeze_password_chain, cherry-picked from upstream:
don't always follow the same path through the password stack on
the PAM_UPDATE_AUTHTOK pass as was used in the PAM_PRELIM_CHECK
pass; this Linux-PAM deviation from the original PAM spec causes a
number of problems, in particular causing wrong return values when
using the refactored pam-auth-update stack. LP: #303515, #305882.
** Changed in: pam (Ubuntu)
Status: New => Fix Released
--
a "new password" failure in a requisite PAM module does not prevent setting
that password
https://bugs.launchpad.net/bugs/198730
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
