[gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/

[gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/

[Sam James]

commit:     204d52b41581306d7fa30dd0634c581b18b8eedc
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 27 06:30:10 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 30 21:18:26 2021 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=204d52b4

Add 2021-06-30-libxcrypt-migration

Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../2021-06-30-libxcrypt-migration.en.txt          | 47 ++++++++++++++++++++++
 1 file changed, 47 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
new file mode 100644
index 0000000..87cfd67
--- /dev/null
+++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
@@ -0,0 +1,47 @@
+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
+News-Item-Format: 2.0
+
+The implementation of libcrypt.so within glibc has been deprecated
+for a long time and will be removed in the near future.
+
+For this reason, we are following other distributions (where
+this has been tested for years already) and switching to the 
+external libxcrypt implementation, starting with ~arch 
+installations.
+
+This will be a regular update, and in nearly all cases you
+will not have to take any action and not observe any problems.
+
+We do recommend, however, that your system is *fully* up
+to date first. This is a standard recommendation but in this
+specific case, it is useful to have a simplified depgraph
+to ensure that Portage is able to smoothly calculate
+an upgrade path.
+
+That is, please take the opportunity to fully upgrade your
+systems now, before the migration occurs, to simplify matters.
+
+This change will occur on 2021-07-14 for ~arch users. Stable
+users will update at a later date.
+
+If for whatever reason you do *not* wish to switch now -
+which is only delaying the inevitable - you
+need to take the following steps:
+* unmask and enable the crypt USE flag of sys-libs/glibc
+* mask the system USE flag of sys-libs/libxcrypt
+* mask >=virtual/libcrypt-2
+
+If you wish to manually migrate now, there are a series
+of steps described on the wiki (see below), but the outline is:
+* unforce the crypt USE flag of sys-libs/glibc and disable it
+* unmask the system and split-usr (if applicable) USE flag of sys-libs/libxcrypt
+and enable it
+* unmask >=virtual/libcrypt-2
+
+For more information, please see:
+* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation
+* https://bugs.gentoo.org/699422

[gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/

[Sam James]

commit:     48149ddf9fcd870bb6ac09a5cd8ded10718f9024
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jul  1 06:50:53 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul  1 06:50:53 2021 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=48149ddf

2021-06-30-libxcrypt-migration: change unmask instruction to use ~ operator

We changed the mask to use ~ for future flexibility.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt | 2 +-
 1 file changed, 1 insertion(+), 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 87cfd67..16b5596 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
@@ -40,7 +40,7 @@ of steps described on the wiki (see below), but the outline is:
 * unforce the crypt USE flag of sys-libs/glibc and disable it
 * unmask the system and split-usr (if applicable) USE flag of sys-libs/libxcrypt
 and enable it
-* unmask >=virtual/libcrypt-2
+* unmask ~virtual/libcrypt-2
 
 For more information, please see:
 * https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation

[gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/

[Sam James]

commit:     3bd3959aa328c89f1ef959bfc342acef117c28a4
Author:     Alexey Sokolov <sokolov <AT> google <DOT> com>
AuthorDate: Thu Jul  1 22:49:22 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jul  5 23:46:43 2021 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=3bd3959a

2021-06-30-libxcrypt-migration: Translate libxcrypt news to Russian

Bug: https://bugs.gentoo.org/699422
Signed-off-by: Alexey Sokolov <sokolov <AT> google.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../2021-06-30-libxcrypt-migration.ru.txt          | 47 ++++++++++++++++++++++
 1 file changed, 47 insertions(+)

diff --git a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.ru.txt b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.ru.txt
new file mode 100644
index 0000000..d52db11
--- /dev/null
+++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.ru.txt
@@ -0,0 +1,47 @@
+Title: Миграция в ~arch с glibc[crypt] на libxcrypt
+Author: Andreas K. Hüttel <dilfridge@gentoo.org>
+Author: Sam James <sam@gentoo.org>
+Translator: Alexey Sokolov <alexey+gentoo@asokolov.org>
+Posted: 2021-06-30
+Revision: 1
+News-Item-Format: 2.0
+
+Реализация библиотеки libcrypt.so в glibc давно устарела и скоро
+будет удалена.
+
+Прочие дистрибутивы годы назад уже переключились на внешнюю
+реализацию под названием libxcrypt. Мы решили последовать их примеру
+и тоже переключиться на libxcrypt. Вначале изменения затронут системы
+на ~arch.
+
+Это будет обычное обновление, и, скорее всего, вам не нужно будет
+предпринимать никаких действий, и проблем возникнуть не должно.
+
+Однако, мы рекомендуем сперва *полностью* обновить систему.
+Это стандартная рекомендация, но в этом конкретном случае
+более простой граф зависимостей поможет portage вычислить
+порядок обновлений.
+
+Так что, чтобы упростить процесс обновления, пожалуйста,
+обновите систему сейчас, до начала самой миграции.
+
+Для пользователей ~arch изменение произойдёт 14 июля 2021,
+пользователи стабильной ветки перейдут на libxcrypt позже.
+
+Если по какой-либо причине вы *не* хотите пока переходить
+на libxcrypt (всего лишь отлагая неизбежное), выполните
+следующие действия:
+* размаскируйте и включите USE-флаг crypt пакета sys-libs/glibc
+* замаскируйте USE-флаг system пакета sys-libs/libxcrypt
+* замаскируйте >=virtual/libcrypt-2
+
+Если вы хотите перейти на libxcrypt уже, точная процедура
+описана в wiki (см. ниже), но суть такая:
+* принудительно выключите USE-флаг crypt пакета sys-libs/glibc
+* размаскируйте USE-флаги system и, если требуется, split-usr
+  пакета sys-libs/libxcrypt
+* размаскируйте ~virtual/libcrypt-2
+
+Дополнительные сведения можно найти здесь:
+* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation
+* https://bugs.gentoo.org/699422

[gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/

[Sam James]

commit:     b941f15ae7ad7e46c89e1ac42495e5d95893cc5a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 20 17:44:48 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 22 23:41:10 2021 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b941f15a

2021-06-30-libxcrypt-migration: mention possible build order problems

Bug: https://bugs.gentoo.org/802210
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 2ba8523..fb16a29 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 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:
+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 Portage's "--keep-going=y".
+
+For more information or troubleshooting tips, 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

[gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/

[Sam James]

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