4 ms·
I'm not talking about "security models", I'm talking about plain correctness of software. Any correctness issue (any "bug") can potentially become a security is
by anyfoo 6y ago
I'm not talking about "security models", I'm talking about plain correctness of software. Any correctness issue (any "bug") can potentially become a security issue if it's reachable through a privilege boundary. And if exploited correctness issues are not in fact the majority of software security issues, they are at least a massive contributor and the subject of this entire discussion.
Examples are a sorted list that inadvertently becomes unsorted while the rest of the program still assumes ordering, or more simply and classically, a pointer that's pointing out of its assumed bounds.
There is no "security model" to consider on that level, and with respect to lockpicking I just wanted to explain why software engineers have access to wonderful tools and methodologies that designers of physical locks don't.
- Normal_gaussian 6y agoI took a slightly different understanding from that comment than I think you did. I took the comment in two parts; the second being a tangential suggestion that security is financial. The first was more interesting. Taken to be a reply to your claim that x=y+1 implies x>y, it is grounded more in theory. The claim is one grounded in a given model - a prevailing mathematical one - and is undoubetdly correct in that model and in the many of the models we use around us. That does not, surprisingly, make it true. There are countless models in which it is false, though it seems unlikely these are useful models. There are also models which are to a degree isomorphic to the current (standard?) models of fancy. In these may lie a way to subvert the expectation of their version of "x>y when x=y+1"