4 ms·
Considering the possibility that any system managed from a compromised device could be compromised to any degree, how does the use of static code analysis and t
by matthewmacleod 13y ago
Considering the possibility that any system managed from a compromised device could be compromised to any degree, how does the use of static code analysis and testing in the future uncompromise those system
It doesn't. But since you were relying on a closed-source system in the first place, you are already screwed - if that's the level of security you require.
- tptacek 13y agoIt wasn't a closed-source system. This bug was in public source code, sitting there for anyone to see it. Nobody did.
- matthewmacleod 13y agoI'm aware that this particular code was - but presumably whichever hypothetical person has arbitrary binaries pushed to them in the grandparent's scenario was using a Mac or iOS.
- brudgers 13y agoServer A is trusted by server B. Danny uses his iPhone to manage server A - ie he accesses server A in a privileged state from his iPhone. If we treat his iPhone as compromised, then the rest of the chain of trust should be treated as comprised all the way through server B. And that's the more difficult exploit to engineer. If Danny is using OSX for administration and we treat his installation as compromised we get a much richer stack for exploiting server A.
- brudgers 13y agoIf Apple isn't dogfooding Macs in its development stack, I'd be surprised. Honest mistake theories drawing upon the mechanisms of Xcode fall away. So, yes, in the big picture Apple is fucked so far as security goes. Short of a source code audit- and from whence come auditors of divine perfection- trust consists of no more than wishful thoughts that the breach was an honest error that went unnoticed by everyone who might have wished to exploit it.
- wglb 13y agoHave you ever looked through the code in OpenSSL?