3 ms·
Ouch! That felt like a longer-than usual list of bugs, especially the memory mgmt bugs leading to arbitrary code execution. And a sizeable number of remotes (i
by uvesten 4y ago
Ouch!
That felt like a longer-than usual list of bugs, especially the memory mgmt bugs leading to arbitrary code execution. And a sizeable number of remotes (if you include webkit in that category.)
I honestly don’t know what to feel; ”great that they fixed so many!” or ”yikes, there are probably millions more like this :(”
- pjmlp 4y agoThat is great, because it is what is causing the business support for safer languages. The amount of hours * salary rate per hour, burned with those security fixes.
- twawaaay 4y agoFor some types of apps, sure. But if you look at the list, the ones that sting the most are kernel or video parsing errors or similar. I am just not seeing these being implemented with anything else than an efficient, low level programming language. At least not for the foreseeable future. But what it may do, hopefully, is getting rid of all that audio/video/photo stuff from the kernel. One has to ask why a video encoder can leak kernel memory in the first place. (This was rhetoric question, we all know why. It is just not sustainable to put more and more stuff into monolithic kernel as you add more silicon to solve some CPU/GPU intensive problems because it is just easy.)
- pjmlp 4y agoAO2 Blue Bottle had video player implemented in Active Oberon, naturally with snippets of Assembly on the hot path. https://gitlab.inf.ethz.ch/felixf/oberon/-/tree/main/source https://gitlab.inf.ethz.ch/felixf/oberon/-/tree/main/source
- Tepix 4y agoWhat difference does it make if there are 3 or 5 remote code execution bugs that were fixed? To me the list seemed pretty ordinary.