Ubuntu
pam package

typo in pam_tally manpage

Bug #772121 reported by Derrick Hudson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pam (Debian)
Fix Released
Undecided
Unassigned
pam (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

The pam_tally manpage says "filed" where it should say "field".

Revision history for this message
Derrick Hudson (dman) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The typo is still present in the upstream source too. You can notify the PAM maintainers or join the mailing list here:
http://www.kernel.org/pub/linux/libs/pam/

Changed in pam (Ubuntu):
status: New → Confirmed
Robert Roth (evfool)
tags: added: manpage
Brian Murray (brian-murray)
tags: added: patch
Steve Langasek (vorlon)
Changed in pam (Ubuntu):
importance: Undecided → Low
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

"Don't use .fail_locktime filed in /var/log/faillog for this user." is still present in 1.3.1-5ubuntu4 on Ubuntu 20.04 (http://manpages.ubuntu.com/manpages/focal/en/man8/pam_tally.8.html)

tags: added: bonic focal xenial
tags: added: bionic
removed: bonic
Revision history for this message
Mathew Hodson (mhodson) wrote :

The pam_tally and pam_tally2 modules have been dropped from Debian in pam 1.4.0-1.

---
Changes:
 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 (Debian):
status: New → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.