Opened 23 months ago

Closed 23 months ago

Last modified 20 months ago

#18025 closed enhancement (fixed)

Linux-PAM-1.5.3

Reported by: Bruce Dubbs Owned by: Tim Tassonis
Priority: normal Milestone: 12.0
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description

New point version.

Change History (7)

comment:1 by Xi Ruoyao, 23 months ago

[Wrong comment removed]

Last edited 23 months ago by Xi Ruoyao (previous) (diff)

comment:2 by Xi Ruoyao, 23 months ago

Release 1.5.3

  • configure: added options to configure stylesheets.
  • configure: added --enable-logind option to use logind instead of utmp in pam_issue and pam_timestamp.
  • pam_modutil_getlogin: changed to use getlogin() from libc instead of parsing utmp.
  • Added libeconf support to pam_env and pam_shells.
  • Added vendor directory support to pam_access, pam_env, pam_group, pam_faillock, pam_limits, pam_namespace, pam_pwhistory, pam_sepermit, pam_shells, and pam_time.
  • pam_limits: changed to not fail on missing config files.
  • pam_pwhistory: added conf= option to specify config file location.
  • pam_pwhistory: added file= option to specify password history file location.
  • pam_shells: added shells.d support when libeconf and vendordir are enabled.
  • Deprecated pam_lastlog: this module is no longer built by default because it uses utmp, wtmp, btmp and lastlog, but none of them are Y2038 safe, even on 64bit architectures. pam_lastlog will be removed in one of the next releases, consider using pam_lastlog2 (from https://github.com/thkukuk/lastlog2) and/or pam_wtmpdb (from https://github.com/thkukuk/wtmpdb) instead.
  • Deprecated _pam_overwrite(), _pam_overwrite_n(), and _pam_drop_reply() macros provided by _pam_macros.h; the memory override performed by these macros can be optimized out by the compiler and therefore can no longer be relied upon.
  • Multiple minor bug fixes, portability fixes, documentation improvements, and translation updates.

comment:3 by Xi Ruoyao, 23 months ago

I've installed it but I don't think it's related to the recent systemd -ftrivial-auto-var-init=zero issue.

comment:4 by Tim Tassonis, 23 months ago

I can take this, I would however not check the systemd/elogind stuff.

comment:5 by Tim Tassonis, 23 months ago

Owner: changed from blfs-book to Tim Tassonis
Status: newassigned

comment:6 by Tim Tassonis, 23 months ago

Resolution: fixed
Status: assignedclosed

Fixed in commit 516e46e3fa

comment:7 by Bruce Dubbs, 20 months ago

Milestone: 11.412.0

Milestone renamed

Note: See TracTickets for help on using tickets.