diff options
| author | Sam Hartman <hartmans@debian.org> | 2021-02-01 17:20:04 -0500 |
|---|---|---|
| committer | Steve Langasek <steve.langasek@canonical.com> | 2021-09-15 17:52:36 -0700 |
| commit | 0330eab989392465ed404c0439773fc526f1e12c (patch) | |
| tree | 1b49c88a85450394c69191ce815a0c04d08952af | |
| parent | 7dec8233c6ce514187804f58e8489c8e819f478a (diff) | |
| download | pam-0330eab989392465ed404c0439773fc526f1e12c.tar.gz pam-0330eab989392465ed404c0439773fc526f1e12c.tar.bz2 pam-0330eab989392465ed404c0439773fc526f1e12c.zip | |
Release 1.4.0-3 to unstable
| -rw-r--r-- | debian/changelog | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/debian/changelog b/debian/changelog index f99a71ee..3d55cd4a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -pam (1.4.0-3) UNRELEASED; urgency=medium +pam (1.4.0-3) unstable; urgency=medium [ Josh Triplett ] * libpam-runtime.postrm: Remove session-noninteractive files on purge, @@ -12,7 +12,7 @@ pam (1.4.0-3) UNRELEASED; urgency=medium * pam-configs/unix: Default to yescript rather than sha512. From a theoretical security standpoint, it looks like yescript has similar security properties, assuming (as we typically do in the crypto protocol community) that sha256 is still reasonable. However, in terms of practical resistant to password cracking, particularly in terms of valuing space complexity as well as time complexity, yescript is superior, Closes: #978553 * No infinite loop on purge of libpam-runtime, Closes: #977648 * patches-applied/pam_faillock_create_directory: create /run/faillock when needed. - + -- Sam Hartman <hartmans@debian.org> Mon, 01 Feb 2021 15:27:08 -0500 |