News for hackers. Stuff that matters.
Re:Writing Exploit-Resistant Code with OpenBSD by anonymousDan on Monday May 06, 2019 @07:34AM (#19838428)
What exactly do you mean by capability based addressing Vs capability object model? Is it the use of capabilities to grant access to particular chunks of memory? What do you see as the pros and cons?
Re:Writing Exploit-Resistant Code with OpenBSD by sebcat on Monday May 06, 2019 @10:17AM (#19839598)
Reposting this from the other day: https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/

Paper: https://www.cl.cam.ac.uk/research/security/ctsrd/pdfs/201406...

"Motivated by contemporary security challenges, we reevaluate and refine capability-based addressing for the RISC era. We present CHERI, a hybrid capability model that extends the 64-bit MIPS ISA with byte-granularity memory protection."

Re:Writing Exploit-Resistant Code with OpenBSD by willvarfar on Monday May 06, 2019 @09:02AM (#19839001)
The Object Capability Model https://en.wikipedia.org/wiki/Object-capability_model is the general approach of tracking priviledges at a fine grain.

Capability-based addressing https://en.wikipedia.org/wiki/Capability-based_addressing is hardware that implements 'fat pointers' that point to ranges of memory so its not possible for a program to address memory it shouldn't. Basically, it forces programs to be 'memory safe' https://en.wikipedia.org/wiki/Memory_safety even if written in memory-unsafe languages such as C.

Re:Writing Exploit-Resistant Code with OpenBSD by nickpsecurity on Monday May 06, 2019 @09:02AM (#19838999)
This free book is probably best place to start:

http://www.cs.washington.edu/homes/levy/capabook/index.html

The surviving, capability architecture is System/38 -> AS/400 -> IBM i. A side effect of better architecture is that they are also incredibly reliable. One person here described them as the tanks of their company's servers.