1.4.0-10ubuntu1 has been uploaded to jammy, which fixes this bug, but a
wrong upload option prevents this bug from being autoclosed.
Related changelog entry:
pam (1.4.0-1) unstable; urgency=medium
* New upstream release. Closes: #948188.
- Stop using obsoleted selinux headers. Closes: #956355.
- Continue building pam_cracklib, which is deprecated upstream;
the replacement, pam_passwdqc, is packaged separately.
- Update symbols file for new symbols.
- Refresh lintian overrides for changes to available pam modules.
* Drop patches to implement "nullok_secure" option for pam_unix.
Closes: #674857, #936071, LP: #1860826.
* debian/patches-applied/cve-2010-4708.patch: drop, applied upstream.
* debian/patches-applied/nullok_secure-compat.patch: Support
nullok_secure as a deprecated alias for nullok.
* debian/pam-configs/unix: use nullok, not nullok_secure.
* Drop pam_tally and pam_tally2 modules, which have been deprecated
upstream in favor of pam_faillock. Closes: #569746, LP: #772121.
* Add hardening+=bindnow to build options, per lintian.
** Changed in: pam (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772121
Title:
typo in pam_tally manpage
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/772121/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
