antiloper

There seems to be a group of actors, both in this thread and the one about the PHP release, that try to convince readers that patching existing PHP installations is not that critical.

I think this group has a good reason for not wanting PHP installations to get patched.

Just how debian was done after weak keys, OpenSSL was done after heartbleed, or Windows was done after (rolls dice) the print spooler RCE

Surely the "structual fix" for a use-after-free is a pile of unreviewed C code! I don't see any problem here.

PHP is tracking its own memory usage internally with limits configurable via php.ini.

> they decided to intentionally not fixing the correctly identified problem

Which problem?

> Computah... build me a social network in PHP. Import the user's profile from GitHub, they shouldn't have to fill anything in. No likes, reposts or algorithms. Add a catchy slogan at the home page. Make no mistakes!

Who is "we" in that sentence? Why are you not speaking for yourself?

Obvious AI generated article without citing any sources.

I mean, obviously? Soldiers operate under different rules than civilians. This has always been true.

> The C vs C++ distinction here is genuinely treacherous

What's so genuine about this?

What are you talking about? The point is in fact to pick all the numbers in the range with exactly the same probability.

See section 7.3.17 of the Intel SDM, and how NIST SP800-90A (which the SDM refers to) defines "random number".

Did you reply to the wrong post?

Searching for products has become impossible. If you don't already know what you are looking for, you're screwed.

Installing docker by default is completely insane. What are they doing? Rootless podman has been around for many years at this point.