public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] pam: Update to version 1.7.3
Date: Fri,  2 Oct 2026 13:23:27 +0200	[thread overview]
Message-ID: <20261002112330.3568361-10-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261002112330.3568361-1-adolf.belka@ipfire.org>

- Update from version 1.7.2 to 1.7.3
- Update of rootfile
- Changelog
1.7.3
	* pam_unix: removed support for creating new DES/bigcrypt hashed passwords.
	  Login with existing DES/bigcrypt passwords is still possible.
	* pam_unix: changed the default hash algorithm from DES to SHA512.
	* pam_unix: always use unix_update helper if SELinux is enabled.
	* pam_unix: fixed option parsing that could silently ignore "quiet" and
	  "minlen=" depending on configuration line order.
	* pam_access: fixed matching of fully qualified usernames.
	* pam_env: fixed buffer allocation that could result in insufficient space.
	* pam_faillock: fixed tally loss under concurrent auth failures that could
	  allow the deny= threshold to be bypassed.
	* pam_faillock: added logging when preauth denies access to a locked account.
	* pam_group: fixed out-of-bounds read in wildcard matching.
	* pam_limits: fixed maxlogins/maxsyslogins limits that could incorrectly
	  deny login.
	* pam_namespace: fixed resource leaks on configuration parse errors.
	* pam_pwhistory: allow earlier passwords when remember count is reduced.
	* pam_selinux: fixed memory leaks and corrected swapped arguments in
	  log messages.
	* pam_sepermit: fixed crash on malformed config lines, hardened lock file
	  handling, and fixed leaking file descriptors on exec.
	* pam_succeed_if: fixed broken ruser matching and prevented logging unknown
	  user names in plaintext.
	* pam_time: fixed out-of-bounds read in wildcard matching, fixed day-of-week
	  parsing, and ignore rules with malformed time fields.
	* pam_umask: validate umask, pri and ulimit values in GECOS.
	* pam_userdb: fixed password comparison timing leak.
	* Multiple minor bug fixes, build fixes, portability fixes,
	  documentation improvements, and translation updates.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 config/rootfiles/common/pam | 5 +++--
 lfs/pam                     | 4 ++--
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/config/rootfiles/common/pam b/config/rootfiles/common/pam
index 18826b21e..5fd9332cc 100644
--- a/config/rootfiles/common/pam
+++ b/config/rootfiles/common/pam
@@ -82,8 +82,6 @@ usr/lib/libpamc.so.0.82.1
 #usr/share/locale/am
 #usr/share/locale/am/LC_MESSAGES
 #usr/share/locale/am/LC_MESSAGES/Linux-PAM.mo
-#usr/share/locale/ar
-#usr/share/locale/ar/LC_MESSAGES
 #usr/share/locale/ar/LC_MESSAGES/Linux-PAM.mo
 #usr/share/locale/as
 #usr/share/locale/as/LC_MESSAGES
@@ -143,6 +141,9 @@ usr/lib/libpamc.so.0.82.1
 #usr/share/locale/it/LC_MESSAGES/Linux-PAM.mo
 #usr/share/locale/ja/LC_MESSAGES/Linux-PAM.mo
 #usr/share/locale/ka/LC_MESSAGES/Linux-PAM.mo
+#usr/share/locale/kab
+#usr/share/locale/kab/LC_MESSAGES
+#usr/share/locale/kab/LC_MESSAGES/Linux-PAM.mo
 #usr/share/locale/kk/LC_MESSAGES/Linux-PAM.mo
 #usr/share/locale/km
 #usr/share/locale/km/LC_MESSAGES
diff --git a/lfs/pam b/lfs/pam
index e2d635480..85c06a65d 100644
--- a/lfs/pam
+++ b/lfs/pam
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 1.7.2
+VER        = 1.7.3
 
 THISAPP    = Linux-PAM-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -45,7 +45,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = d7ebfac4393af3f889fef973946f1e6d60f118f2e048448708c5fdf0ef7fa7780945cda3b0abf6e0e2e15bbc2dd23be52389efabd00647381b3bc971f1aadcd8
+$(DL_FILE)_BLAKE2 = 2476e5b08f8e4c3e013f8ee22d858da79e9074160d396b504400c1f7ee490df9b432b226d18ae58e6f5c77a0a31709d363b76c800cd86953237f7e534a317358
 
 install : $(TARGET)
 
-- 
2.55.0



  parent reply	other threads:[~2026-10-02 11:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 11:23 [PATCH] core205: Ship gdb Adolf Belka
2026-10-02 11:23 ` [PATCH] core205: Ship libpng Adolf Belka
2026-10-02 11:23 ` [PATCH] core205: Ship pam Adolf Belka
2026-10-02 11:23 ` [PATCH] freeradius: Update to version 3.2.10 Adolf Belka
2026-10-02 11:23 ` [PATCH] gdb: Update to version 18.1 Adolf Belka
2026-10-02 11:23 ` [PATCH] git: Update to version 2.56.0 Adolf Belka
2026-10-02 11:23 ` [PATCH] iperf3: Update to version 3.22 Adolf Belka
2026-10-02 11:23 ` [PATCH] libpng: Update to version 1.6.59 Adolf Belka
2026-10-02 11:23 ` [PATCH] ntfs-3g: Update to version 2026.9.28 Adolf Belka
2026-10-02 11:23 ` Adolf Belka [this message]
2026-10-02 11:23 ` [PATCH] pcre2: Update to version 10.49 Adolf Belka
2026-10-02 11:23 ` [PATCH] shairport-sync: Update to version 5.5.2 Adolf Belka
2026-10-02 11:23 ` [PATCH] swtpm: Update to version 0.10.2 Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261002112330.3568361-10-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox