Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zevii6xx.fsf@gentoo.org>
Date: Mon, 09 Nov 2026 11:24:10 +0000
From: Sam James <sam@...too.org>
To: Andreas Schwab <schwab@...e.de>
Cc: Alejandro Colomar <alx+linux-man@...nel.org>,  Walter Harms
 <wharms@....de>,  "linux-man@...r.kernel.org" <linux-man@...r.kernel.org>,
  Rich Felker <dalias@...c.org>,  libc-alpha@...rceware.org,
  musl@...ts.openwall.com,  ~hallyn/shadow@...ts.sr.ht
Subject: Re: RFC: how to document musl-crypt failure ?

Andreas Schwab <schwab@...e.de> writes:

> On Nov 09 2026, Alejandro Colomar wrote:
>
>> I've CCed Rich and also musl and glibc, since they probably want to
>> comment.  I've also CCd shadow-utils.
>
> libcrypt is no longer part of glibc, it is now provided by libxcrypt.

Indeed. But while we're here..

For libxcypt, it's determined by the configure option:
--disable-error-tokens. By default, error tokens are enabled.

I've switched Gentoo to use --disable-*. Fedora already did many years
ago so package failures should be smoked out by now:
* https://src.fedoraproject.org/rpms/libxcrypt/c/853ed305cd53c67bb2827dce78b889c8d187e1e0?branch=rawhide
* https://bugzilla.redhat.com/show_bug.cgi?id=1611784

Debian uses the libxcrypt default. I didn't check other distros yet.

sam

Download attachment "signature.asc" of type "application/pgp-signature" (419 bytes)

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.