[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5da1914e-c77a-f341-ad3d-5979311a134e@mirbsd.de>
Date: Fri, 6 Nov 2026 23:21:51 +0100 (CET)
From: Thorsten Glaser <tg@...bsd.de>
To: musl@...ts.openwall.com
Subject: examples of breakage (was Re: Advisory for OpenSSH+musl
users)
Dixi quod…
>On Fri, 6 Nov 2026, Loganaden Velvindron wrote:
>
>>Do you have the list of software which were breaking and which caused
>>this change in musl in the first place (commit:b3c4cc121f70f) ?
>
>No full list, but, the reverse change in GNU glibc/libxcrypt (begin
>to return NULL) broke at least:
>
>• GNU CVS
>• shadow-tools
>• cyrus-sasl2 (CVE-2013-4122)
>• xlock
I’ve gotten more on Fedi¹:
• The su and passwd utilities in Minix 2.
• The dial-auth PAM module in current Illumos.
Also, a link to: https://news.ycombinator.com/item?id=50383920
But even the (yeah, nōn-normative, I know, but still relevant)
example from POSIX (2004) does:
if (strcmp(p->pw_passwd, crypt(oldpasswd, p->pw_passwd)) == 0) {
Meaning, if we *know* it’s supported (and not ENOSYS), we *can*
assume it doesn’t return NULL, for all practical values of know.
(Except for glibc/libxcrypt since 2013, apparently.)
① https://tty0.social/@JdeBP/117567251944142305
bye,
//mirabilos
--
Yes, I hate users and I want them to suffer.
-- Marco d'Itri on gmane.linux.debian.devel.general
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
