Hello Alex,
Am Mon, Sep 01, 2025 at 10:01:10AM +0200 schrieb Alejandro Colomar:

On Sun, Aug 24, 2025 at 02:48:37PM +0000, Helge Kreutzmann wrote:

quoted

Without further ado, the following was found:

Issue:    "fail closed"??

"The behavior of E<.Nm crypt> on errors isn't well standardized.  Some "
"implementations simply can't fail (except by crashing the program), others "
"return a null pointer or a fixed string.  Most implementations don't set "
"E<.Va errno>, but some do.  POSIX specifies returning a null pointer and "
"setting E<.Va errno>, but it defines only one possible error, E<.Er ENOSYS>, "
"in the case where E<.Nm crypt> is not supported at all.  Some older "
"applications are not prepared to handle null pointers returned by E<.Nm "
"crypt>.  The behavior described above for this implementation, setting E<.Va "
"errno> and returning an invalid hash different from E<.Fa setting>, is "
"chosen to make these applications fail closed when an error occurs."

I don't see any of this text in this page, nor in its git history.
Please check.

Sorry, this is comming from libxcrypt, i.e.
https://github.com/besser82/libxcrypt

So please ignore this report, I fixed our internal assignement.

Greetings

         Helge

-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/