From: Walter Harms <wharms@bfs.de>
To: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: RFC: how to document musl-crypt failure ?
Date: Mon, 9 Nov 2026 08:59:19 +0000 [thread overview]
Message-ID: <ad592d57700043c181886d95b2564e6b@bfs.de> (raw)
Hello list,
in case someone missed it: musl crypt() had an documented but unexpected behavier that caused
a lot of trouble. See: https://news.ycombinator.com/item?id=50377221 SSHHole.com CVE-2026-123158
Normaly i would step over it but in this special case ... it would like to start a discussion if we should mention
that in a note to crypt(). Perhaps recommending an additional check for '*' ? I am not sure but this is a very special case ...
CU
next reply other threads:[~2026-11-09 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:59 Walter Harms [this message]
2026-11-09 10:10 ` RFC: how to document musl-crypt failure ? Alejandro Colomar
2026-11-09 10:23 ` Andreas Schwab
2026-11-09 11:24 ` Sam James
2026-11-09 13:56 ` [musl] " Rich Felker
2026-11-09 15:50 ` Alejandro Colomar
2026-11-12 14:37 ` Alejandro Colomar
2026-11-12 14:45 ` Rich Felker
2026-11-12 15:01 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad592d57700043c181886d95b2564e6b@bfs.de \
--to=wharms@bfs.de \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.