Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah, but with how we’re moving towards running each (desktop) application in its own cgroup, thus restricting what syscalls any given application can do, soon any old user process will no longer be able to read any other process’s memory. I don’t believe that the argument about how we need not patch a hole because another one exists right besides it is sound.


> I don’t believe that the argument about how we need not patch a hole because another one exists right besides it is sound.

It is when you are essentially putting bars in front of your windows while leaving the front door unlocked, i.e. you are making things worse in the name of security while not actually providing any additional security.

> Yeah, but with how we’re moving towards running each (desktop) application in its own cgroup, thus restricting what syscalls any given application can do

Who is we? I don't want or need any of that on my free software system.


I agree. My point was only that this hole can easily be patched in X as well. So the argument was essentially "we do not bother to patch it with X, so we must rewrite X".


It was my understanding that changing the original codebase to fix it would’ve been involved enough as to warrant a rewrite.


I think this is nonsense.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: