Cyber ·
crypt() error behavior varies across implementations, notes oss-sec discussion
An oss-sec list post dated November 5, 2026 notes that crypt() behaves differently on errors depending on the implementation. According to the quoted portability notes, POSIX specifies a null pointer return and errno, but defines only ENOSYS as a possible error.
The item is a message by Michael Orlitzky, reproduced through automatic translation in the oss-sec list feed, dated November 5, 2026. The subject is how the libc crypt() function behaves when an error occurs. According to the quoted portability notes, this behavior is not well standardized: some implementations cannot fail, except by crashing the program; others return a null pointer or a fixed string. Some set errno, and most do not.
The source also records that POSIX specifies a null pointer return and the setting of errno, but lists only one possible error, ENOSYS, for the case where crypt is not supported at all. The text in the feed is truncated, and the title refers to a password authentication bypass in OpenSSH combined with musl libc. To check the full scope, consult the original address indicated in the item on the oss-sec list, read the complete message and the thread replies, and verify details before drawing conclusions about specific systems.
Original source: Re: “sshole”: desvio da autenticação por senha no OpenSSH + musl libc