2 ms·
Sorry to hear that. Yeah, they're not as strong for C++ yet as it's more complex and has less R&D in that sector. My idea for C++ would be to try to find or eve
by nickpsecurity 11y ago
Sorry to hear that. Yeah, they're not as strong for C++ yet as it's more complex and has less R&D in that sector. My idea for C++ would be to try to find or even encourage development of those that catch the interface and concurrency errors at the least. So, that's Design-by-Contract [1] [2] along with something like ConSeq [3] if it's available or usable for your build. D-by-C, done right, gets a lot of mileage w/ ConSeq showing promise.
Do keep the exploit mitigation tech, though. The NaCl paper was one of best reads I had that year. Most interesting one right now is Code Pointer Integrity [4]. Curious, is there a configuration that swaps out the sandbox for something with the same interface but no real sandbox? Point is if we can swap out the existing sandbox (esp CFI) for a different technology (eg CPI, Softbound + CETS).
[1] http://www.drdobbs.com/an-exception-or-a-bug/184401686 http://www.drdobbs.com/an-exception-or-a-bug/184401686
[2] http://www.codeproject.com/Articles/8293/Design-by-Contract-in-C http://www.codeproject.com/Articles/8293/Design-by-Contract-...
[3] https://webcache.googleusercontent.com/search?q=cache:WZAQPu7dJgQJ:research.cs.wisc.edu/wpis/papers/asplos11.pdf+&cd=3&hl=en&ct=clnk&gl=us https://webcache.googleusercontent.com/search?q=cache:WZAQPu...
[4] https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-kuznetsov.pdf https://www.usenix.org/system/files/conference/osdi14/osdi14...