[arch-dev-public] retracting libxcrypt 4.4.22-1 from [testing]
Hello everybody, the testing package libxcrypt 4.4.22-1 was reported to be bad... Andreas was forced to change his password on login, which resulted in him being locked out of his system. We are trying to clarify... So I removed libxcrypt from [testing] for the time being. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
Christian Hesse via arch-dev-public
Hello everybody,
the testing package libxcrypt 4.4.22-1 was reported to be bad... Andreas was forced to change his password on login, which resulted in him being locked out of his system. We are trying to clarify...
So I removed libxcrypt from [testing] for the time being.
I found the real issue: Our pam configurations for 'login' and 'su' were missing the configuration for 'password', thus updating expired password failed. This is now fixed in util-linux 2.37-2, which will move with libxcrypt 4.4.22. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
participants (1)
-
Christian Hesse