@airtower Okay, there's actually a bit more going on here.
The libxcrypt design still only accidentally avoids triggering the same openssh "bug". [1]
The musl also has a similar "if passed *, then return x as invalid on errors". (not in the too long sha512 case, but than cannot be reached by * as setting input anyway. So this is confusing to read, but afaict as correct as libxcrypt.
The one saving grace of the libxcrypt implementation is that ~nobody has a literal `*0` set as their hash.
1/2