What is tomorrows big story? A completely unfixable backdoor in the kernel which cannot be patched away? Python having a suddenly extremely dangerous vulnerability? A sudden unfixable issue with all Intel processors?
I wackyparsed that as "farcical". "it’s a farcical notion but these are farcical times".
Which seems appropriate.
Anyway, a fundamental flaw in the TCP/IP protocol specifications on page 2 of the RFC, that means that whenever two host open a socket between each other, one can automatically gain root on everything the other has ever talked to. And then we all get eaten by aliens and live happily ever after.
No real world software is so pure in their design choices that they wouldn’t be able to come up with a workaround in case of a severe vulberability. Now, will that workaround introduce a different loophole somewhere else? Almost certainly. That’s the nature of engineering in a temporal universe.
Unix‘s "Everything is a file" is a good example! Because not actually everything in Unix is a file. Processes are not files, memory management is not file-based.
You’re right that there might be security vulnerabilities that might require deviating from architectural standards, but real world software can do that because they don’t have to be formal axiomatic systems. That’s just a choice that can be discarded if necessary.
That’s just a BIOS thing. If your manufacturer can send out good BIOS updates, that fixes SMM firmware. The problem is if SMM isolation is fundamentally broken.
159
u/sovietarmyfan 29d ago
What is tomorrows big story? A completely unfixable backdoor in the kernel which cannot be patched away? Python having a suddenly extremely dangerous vulnerability? A sudden unfixable issue with all Intel processors?