| |||||||||||||
Attacking hardened Linux systems with kernel JIT sprayingAttacking hardened Linux systems with kernel JIT sprayingPosted Nov 19, 2012 16:40 UTC (Mon) by drag (subscriber, #31333)In reply to: Attacking hardened Linux systems with kernel JIT spraying by khim Parent article: Attacking hardened Linux systems with kernel JIT spraying
It's better to have buggy code that works now then it is to have something that may work in 30 years.
(Log in to post comments)
Attacking hardened Linux systems with kernel JIT spraying Posted Nov 20, 2012 3:07 UTC (Tue) by liam (subscriber, #84133) [Link]
Is there any reason why this work couldn't be done it parallel with kernel development?
There are parts of the kernel that are only touched rarely (ex. block/deadline-iosched, though there are probably better examples). It seems as though this type of analysis might be good long term project. Of course, if it is truly infeasible for any but the least interesting parts of the kernel then it is a waste of time.
Attacking hardened Linux systems with kernel JIT spraying Posted Nov 20, 2012 19:15 UTC (Tue) by mathstuf (subscriber, #69389) [Link]
> Of course, if it is truly infeasible for any but the least interesting parts of the kernel then it is a waste of time.
I suppose that since there's a high chance of it happening, the question boils down to: "What wins when the decision is between ABI compatibility and provably secure?"
|
|||||||||||||