[gentoo-dev] [PATCH 1/2] 2021-06-30-libxcrypt-migration: mention PAM/md5crypt issues

[gentoo-dev] [PATCH 1/2] 2021-06-30-libxcrypt-migration: mention PAM/md5crypt issues

[Sam James]

Bug: https://bugs.gentoo.org/802267
Bug: https://bugs.gentoo.org/802807
Signed-off-by: Sam James <sam@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..5a78036 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 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 passwrd 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
-- 
2.32.0

[gentoo-dev] [PATCH 2/2] 2021-06-30-libxcrypt-migration: mention possible build order problems

[Sam James]

Bug: https://bugs.gentoo.org/802210
Signed-off-by: Sam James <sam@gentoo.org>
---
 .../2021-06-30-libxcrypt-migration.en.txt                | 9 +++++++++
 1 file changed, 9 insertions(+)

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 5a78036..e1a7ac5 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
@@ -48,9 +48,18 @@ a bug in PAM [0][1] may mean that you were unable to login. We recommend
 using `passwd` to change/refresh your passwrd so it is using modern
 methods. A new version of PAM has been added to the tree to resolve this issue.
 
+In some cases, Portage may schedule a rebuild of certain packages in an
+incorrect order [2]. If building a package fails, please try upgrading
+libcrypt and libxcrypt first:
+
+# emerge -v1 virtual/libcrypt sys-libs/libxcrypt
+
+And then continue the world upgrade with --keep-going=y.
+
 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
+[2] https://bugs.gentoo.org/802210
-- 
2.32.0

Re: [gentoo-dev] [PATCH 1/2] 2021-06-30-libxcrypt-migration: mention PAM/md5crypt issues

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

>>>>> On Tue, 20 Jul 2021, Sam James wrote:

> -Revision: 1
> +Revision: 2

Is this supposed to be read again by users? Then it should be a new news
item (with updated date in filename) and the old item should be deleted.

> +Please note that if you last changed your password before ~2008,
> +it may using md5crypt or similar other weak mechanisms in /etc/shadow;

This should be "may be using" or "may use" I think.

s/similar other/similar/

> +a bug in PAM [0][1] may mean that you were unable to login. We recommend
> +using `passwd` to change/refresh your passwrd so it is using modern

s/passwrd/password/

Also, this is read as plain text, so maybe use double quotes instead of
accents graves.

> +methods. A new version of PAM has been added to the tree to resolve this issue.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

Re: [gentoo-dev] [PATCH 1/2] 2021-06-30-libxcrypt-migration: mention PAM/md5crypt issues

[Sam James]

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]



> On 20 Jul 2021, at 20:57, Ulrich Mueller <ulm@gentoo.org> wrote:
> 
>>>>>> On Tue, 20 Jul 2021, Sam James wrote:
> 
>> -Revision: 1
>> +Revision: 2
> 
> Is this supposed to be read again by users? Then it should be a new news
> item (with updated date in filename) and the old item should be deleted.

Sure, I'll do that.
> 
>> +Please note that if you last changed your password before ~2008,
>> +it may using md5crypt or similar other weak mechanisms in /etc/shadow;
> 
> This should be "may be using" or "may use" I think.
> 
> s/similar other/similar/

Thanks!

> 
>> +a bug in PAM [0][1] may mean that you were unable to login. We recommend
>> +using `passwd` to change/refresh your passwrd so it is using modern
> 
> s/passwrd/password/
> 
> Also, this is read as plain text, so maybe use double quotes instead of
> accents graves.

Sure.

> 
>> +methods. A new version of PAM has been added to the tree to resolve this issue.

Cheers for the review,
sam

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]