![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Probably wiping process control code from the systems that contain tons of fiddly hard to find constants and other information.
Probably wiping process control code from the systems that contain tons of fiddly hard to find constants and other information.
Why yes, I would like my stack traces to make no ffing sense! I’m so glad you asked.
I wouldn’t trust the Java app sandbox at all. They basically abandoned it.
Based on the comments it appears the prompt doesn’t really even fully work. It mainly seems to be something to laugh at while despairing over the writer’s nonexistant command of logic.
I’m a bit concerned what happens when Gabe Newell dies
The thing is the whole c program is unsafe. In rust individual parts are marked unsafe. This means auditing should be easier. Also being always on your toes isn’t really viable. Breaking down the program into safe vs unsafe is probably an improvment
In cases where bugs have been counted they tended to make up the majority of vulnerabilities. Chrome, Firefox, and Windows reported that around 70% of security vulnerabilites were memory corruption. Yes a subset, but the majority of the worst subset.
if you are looking for a HURD based stable OS you are a bit out of luck.