Spyke

Replies

Comment on

LiveOverflow - php situation 24h later (YouTube)

Reply in thread

I think Debian is probably pretty conservative in their updates. I also recommend checking out the needrestart package. It will tell you when a reboot is needed because of a newer kernel that was installed, or when a systemd service needs a restart.

But as another commenter noted, outside of self hosting, in enterprise businesses environments where you manage an army of servers, things look different. But then, these guys are paid to be on-call in the weekend for events like these. :)

Comment on

LiveOverflow - php situation 24h later (YouTube)

Reply in thread

Yeah, for businesses I can see that, but selfhosting, meh. I have just one personal server firewalled and Wireguarded, so the PHP vulnerability wasn't even publicly exposed. Even so, I have never had any issues with Debian's unattended security upgrades in the last 5 years.

In enterprise environments with a hundred servers, though, you will want to do something else than I do. :)

But even then, don't enterprises run a good WAF in front of their public web sites that would have received the patch automatically?

xkcd

Comment on

xkcd #3184: Funny Numbers

Reply in thread

42 is from The Hitchhiker’s Guide to the Galaxy by Douglas Adams. They built an enormous computer called Deep Thought that was the most powerful ever built to calculate the answer to the Ultimate Question of Life, the Universe and Everything. The computer, after 75 million years of processing, came up with 42. The confused crowd that gathered to hear the answer did not understand. Turns out, 42 is the correct answer, but what is the question?

So after that, they decide to build another computer, which is planet Earth, to figure out the question.

It was still calculating when it was destroyed by the Vogons to make space for a hyperspace bypass.

Comment on

Programmer Profession

Stack Overflow usage has always come with the condition that you understood what the answer was doing and that it actually applied to your problem, on top of feeling that it looked like a high quality solution to it instead of crappy code. I mean, I guess in that sense, the people who blindly copied everything from the internet were the first vibe coders…

Comment on

Oops, something went wrong!

Reply in thread

Iit’s an internal error that is not handled properly. They don’t want to tell you the exact error message and detailed information around that, because it would expose the internal state of the backend and that would be a security issue. There is really nothing more that they can tell you, except that a developer needs to look at this (and possibly thousands to tens or hundreds of thousands of similar logged errors) and they probably already are.