Issue in man page

[hmartink]

'''Dear libxcrypt maintainer,
the manpage-l10n project[1] maintains a large number of translations of
man pages both from a large variety of sources (including libxcrypt) as
well for a large variety of target languages.

During their work translators notice different possible issues in the
original (english) man pages. Sometimes this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a
convention not held up and sometimes we simply do not understand the
original.

We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
your latest upstream version once in a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.

Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to convert into
your source format.

Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.

I'm now reporting the issue for your project. If future reports
should use another channel, please let me know.

[1] https://manpages-l10n-team.pages.debian.net/manpages-l10n/

Man page: crypt.3
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."
'''