TBH that sounds like a straight up bug in that it deviates dangerously from the spec.

Which is notable because musl is more known for adhering to the spec to the point where they break programs that assume nonstandard behavior.

▲

silisili an hour ago | parent [-]

> adhering to the spec

Pedantic, but more "author's understanding of the spec" which isn't always correct.

> assume nonstandard behavior

I go back and forth on this one (spec vs standard behavior). It feels like at some point the most widely used impl -is- the spec, as we've seen in other places (web standards).

	▲	mort96 an hour ago \| parent [-]
		The spec is pretty unambiguous here: https://pubs.opengroup.org/onlinepubs/9799919799/functions/c... > Upon successful completion, crypt() shall return a pointer to the hashed password [...]. Otherwise, it shall return a null pointer and set errno to indicate the error.