From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/
Date: Thu, 22 Jul 2021 23:41:23 +0000 (UTC) [thread overview]
Message-ID: <1626997269.d6020a98d364bbc0c0c8f8d5f5efde5bcb1b383e.sam@gentoo> (raw)
commit: d6020a98d364bbc0c0c8f8d5f5efde5bcb1b383e
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 20 17:42:12 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 22 23:41:09 2021 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=d6020a98
2021-06-30-libxcrypt-migration: mention PAM/md5crypt issues
Bug: https://bugs.gentoo.org/802267
Bug: https://bugs.gentoo.org/802807
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../2021-06-30-libxcrypt-migration.en.txt | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
index 16b5596..2ba8523 100644
--- a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
+++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
@@ -2,7 +2,7 @@ Title: migrating from glibc[crypt] to libxcrypt in ~arch
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Author: Sam James <sam@gentoo.org>
Posted: 2021-06-30
-Revision: 1
+Revision: 2
News-Item-Format: 2.0
The implementation of libcrypt.so within glibc has been deprecated
@@ -42,6 +42,15 @@ of steps described on the wiki (see below), but the outline is:
and enable it
* unmask ~virtual/libcrypt-2
+Please note that if you last changed your password before ~2008,
+it may be using md5crypt or similar other weak mechanisms in /etc/shadow;
+a bug in PAM [0][1] may mean that you were unable to login. We recommend
+using "passwd" to change/refresh your password so it is using modern
+methods. A new version of PAM has been added to the tree to resolve this issue.
+
For more information, please see:
* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation
* https://bugs.gentoo.org/699422
+
+[0] https://bugs.gentoo.org/802267
+[1] https://bugs.gentoo.org/802807
next reply other threads:[~2021-07-22 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 23:41 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-22 23:41 [gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/ Sam James
2021-07-05 23:46 Sam James
2021-07-01 6:51 Sam James
2021-06-30 21:18 Sam James
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=1626997269.d6020a98d364bbc0c0c8f8d5f5efde5bcb1b383e.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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