Re:Why was "goto fail;" added without any other change to th...
by matthewmacleod on Friday February 28, 2014 @11:57AM
(#7319914)
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.
Re:Why was "goto fail;" added without any other change to th...
by tptacek on Friday February 28, 2014 @11:58AM
(#7319926)
It wasn't a closed-source system. This bug was in public source code, sitting there for anyone to see it. Nobody did.
Re:Why was "goto fail;" added without any other change to th...
by matthewmacleod on Friday February 28, 2014 @12:03PM
(#7319962)
I'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.
Re:Why was "goto fail;" added without any other change to th...
by brudgers on Friday February 28, 2014 @12:36PM
(#7320191)
Server 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.
Re:Why was "goto fail;" added without any other change to th...
by brudgers on Friday February 28, 2014 @12:21PM
(#7320093)
If 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.
Re:Why was "goto fail;" added without any other change to th...
by wglb on Friday February 28, 2014 @06:06PM
(#7322155)
Have you ever looked through the code in OpenSSL?
Re:Why was "goto fail;" added without any other change to th...
by marvy on Tuesday March 04, 2014 @07:00PM
(#7344195)
Whenever someone brings up the "trusting trust" thingy, I feel compelled to point out the antidote:
http://www.dwheeler.com/trusting-trust/
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 systems?
Short of finding a unicorn and seeing who can ride it, there's no guarantee that a system isn't pwnd or connected to one that's pwnd. The certificate failure means binaries could have been pushed.
The problem is that you can't trust trust.
http://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thomps...