3 ms·
4 bit keys seems a bit limiting... I could imagine lots of scenarios where a 1 in 16 chance of an exploit succeeding is still a big issue...
by londons_explore 6y ago
4 bit keys seems a bit limiting... I could imagine lots of scenarios where a 1 in 16 chance of an exploit succeeding is still a big issue...
- flohofwoe 6y agoIMHO it's less of a security feature, and more of a debugging aid (the overlap with security is when a failed check causes program termination). You might get more fine-grained overflow checks (vs guard pages), or dangling pointer checks (depending on how that key is stored, e.g. more than one key per memory page?). It's faster then doing the same in code (e.g. via 'tagged handles': https://floooh.github.io/2018/06/17/handles-vs-pointers.html https://floooh.github.io/2018/06/17/handles-vs-pointers.html), or memory debugging tools like Valgrind or clang ASAN (and unlike Valgrind or ASAN, the checks are always enabled, also in the "release version").
- robocat 6y agoIn the most extremely sensitive environments: 1. It still helps with defence in depth 2. The threat of detection prevents attackers that need 100% stealth 3. Failures are likely to be detected which is still valuable as you can now mitigate damage 4. Failures are likely to be detected which helps get software faults fixed - which allows the ecology of security to improve over time