1 |
commit: 232dd42f93031207d628903f6ad4d5c9a96267af |
2 |
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> |
3 |
AuthorDate: Mon Oct 18 20:45:09 2021 +0000 |
4 |
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> |
5 |
CommitDate: Mon Oct 18 20:45:09 2021 +0000 |
6 |
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=232dd42f |
7 |
|
8 |
Add stable version of libxcrypt-migration news |
9 |
|
10 |
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org> |
11 |
|
12 |
.../2021-10-18-libxcrypt-migration-stable.en.txt | 64 ++++++++++++++++++++++ |
13 |
1 file changed, 64 insertions(+) |
14 |
|
15 |
diff --git a/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt |
16 |
new file mode 100644 |
17 |
index 0000000..ccfcddd |
18 |
--- /dev/null |
19 |
+++ b/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt |
20 |
@@ -0,0 +1,64 @@ |
21 |
+Title: migrating from glibc[crypt] to libxcrypt in stable |
22 |
+Author: Andreas K. Hüttel <dilfridge@g.o> |
23 |
+Author: Sam James <sam@g.o> |
24 |
+Posted: 2021-10-18 |
25 |
+Revision: 1 |
26 |
+News-Item-Format: 2.0 |
27 |
+ |
28 |
+The implementation of libcrypt.so within glibc has been deprecated |
29 |
+for a long time and will be removed in the near future. |
30 |
+ |
31 |
+For this reason, we are following other distributions (where |
32 |
+this has been tested for years already) and switching to the |
33 |
+external libxcrypt implementation, now also in stable installations. |
34 |
+ |
35 |
+This will be a regular update, and in nearly all cases you |
36 |
+will not have to take any action and not observe any problems. |
37 |
+ |
38 |
+We do recommend, however, that your system is *fully* up |
39 |
+to date first. This is a standard recommendation but in this |
40 |
+specific case, it is useful to have a simplified depgraph |
41 |
+to ensure that Portage is able to smoothly calculate |
42 |
+an upgrade path. |
43 |
+ |
44 |
+That is, please take the opportunity to fully upgrade your |
45 |
+systems now, before the migration occurs, to simplify matters. |
46 |
+ |
47 |
+This change will occur on 2021-11-01 for stable users. |
48 |
+~arch users by default should already have switched. |
49 |
+ |
50 |
+If for whatever reason you do *not* wish to switch now - |
51 |
+which is only delaying the inevitable - you |
52 |
+need to take the following steps: |
53 |
+* unmask and enable the crypt USE flag of sys-libs/glibc |
54 |
+* mask the system USE flag of sys-libs/libxcrypt |
55 |
+* mask >=virtual/libcrypt-2 |
56 |
+ |
57 |
+If you wish to manually migrate now, there are a series |
58 |
+of steps described on the wiki (see below), but the outline is: |
59 |
+* unforce the crypt USE flag of sys-libs/glibc and disable it |
60 |
+* unmask the system and split-usr (if applicable) USE flag of sys-libs/libxcrypt |
61 |
+and enable it |
62 |
+* unmask ~virtual/libcrypt-2 |
63 |
+ |
64 |
+Please note that if you last changed your password before ~2008, |
65 |
+it may be using md5crypt or similar other weak mechanisms in /etc/shadow; |
66 |
+a bug in PAM [0][1] may mean that you were unable to login. We recommend |
67 |
+using "passwd" to change/refresh your password so it is using modern |
68 |
+methods. A new version of PAM has been added to the tree to resolve this issue. |
69 |
+ |
70 |
+In some cases, Portage may schedule a rebuild of certain packages in an |
71 |
+incorrect order [2]. If building a package fails, please try upgrading |
72 |
+libcrypt and libxcrypt first: |
73 |
+ |
74 |
+# emerge -v1 virtual/libcrypt sys-libs/libxcrypt |
75 |
+ |
76 |
+And then continue the world upgrade with Portage's "--keep-going=y". |
77 |
+ |
78 |
+For more information or troubleshooting tips, please see: |
79 |
+* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation |
80 |
+* https://bugs.gentoo.org/699422 |
81 |
+ |
82 |
+[0] https://bugs.gentoo.org/802267 |
83 |
+[1] https://bugs.gentoo.org/802807 |
84 |
+[2] https://bugs.gentoo.org/802210 |