If you want that behavior you can make a macro which does an assert() after the malloc. C is about giving you the power even if 99% of the time the error should be considered fatal.

You have the order reversed. It used to say null on error. Now it says * on error if so configured (which by default it is).

You are mistaken. That's a 2019 and a 2025 man page. The 2025 man page allows "*".

Consider these two man pages:

Debian Linux 5 years ago: https://manpages.debian.org/bu...

Debian Linux now: https://manpages.debian.org/tr...

You're looking at an older copy of the crypt man page. Compare the two from current Debian and Debian from 5 years ago. Current Debian returns a string starting with "*" so that older applications fail closed (as explained in the man page).

https://manpages.debian.org/tr...
https://manpages.debian.org/bu...

They're renting the ability to access the Internet via a white house IP address. Has nothing to do with email.

Although if you really want a whitehouse email address I could hook you up on whitehouse.net.

For legacy reasons, Crypt() is not allowed to return a null pointer. Some old applications do not expect a null pointer and will crash. On error, it instead returns a string that starts with *. In GNU C the string starts with * and then has a partial, invalid hash. In Musl C it just has the *. Crypt() never returns * on success.

Check the man page.

No, if you read the man page for crypt, a failed return is supposed to start with the "*" character while a successful run will not contain a * character anywhere. GNU libc returns a * followed by additional characters while musl C only returns the *. OpenSSH failed to check whether the crypt output started with *, signaling an error.

That's an OpenSSH bug.

Firefox losing to Edge has more to do with the long-term enshitification of Firefox than any anti-competive behavior by Microsoft. Google Chrome trounces Edge despite Microsoft.

I don't need "real improvements." If it works the same tomorrow that it did yesterday but with just enough change to fix security bugs and keep working with the web sites I visit then it has done what I want it to do.

My windowing system has a theme. One I'm comfortable with. Please use it and stop going off and doing your own kooky thing.

Was it a good story? If it was an engaging read then why care whether AI was used to help write it.

The simplest and most likely explanation is that the license ran out and the copyright owner wanted too much money or some other onerous condition, so google decided to wait until the next satellite pass when they'll get all the imagery.

Unanalyzed raw video. Internet noise. Those would qualify as, "a whole lot of garbage that someone could possibly, maybe analyze to make some statistical inferences about conceivably sensitive data."