SoylentNews is people
SoylentNews
from the one-bad-apple-spoils-the-whole-bunch dept.
Papas Fritas writes:
"Last October, Bruce Schneier speculated that the three characteristics of a good backdoor are a low chance of discovery, high deniability if discovered, and minimal conspiracy to implement. He now says that the critical iOS and OSX vulnerability that Apple patched last week meets these criteria, and could be an example of a deliberate change by a bad actor:
Look at the code. What caused the vulnerability is a single line of code: a second "goto fail;" statement. Since that statement isn't a conditional, it causes the whole procedure to terminate ... Was this done on purpose? I have no idea. But if I wanted to do something like this on purpose, this is exactly how I would do it.
He later added that 'if the Apple auditing system is any good, they will be able to trace this errant goto line to the specific login that made the change.'
Steve Bellovin, professor of Computer Science in Columbia University and Chief Technologist of the Federal Trade Commission, has another take on the vulnerability: 'It may have been an accident; If it was enemy action, it was fairly clumsy.'"
(Score: 2) by frojack on Sunday March 02 2014, @08:46PM
Wait, What?
An arbitrary GOTO, not subordinate to any conditional means that ALL subsequent lines up to the next label are unreachable. The second consecutive goto was totally unconditional.
You don't need optimization passes to detect that, it is basic compiler theory,
Hell, In the past have used code Editors built into IDEs that will detect that.
No, you are mistaken. I've always had this sig.
(Score: 2) by mojo chan on Sunday March 02 2014, @09:55PM
Sure, I was just stating why they disabled the feature. It wasn't reliable, the output changed based on the optimization level.
const int one = 65536; (Silvermoon, Texture.cs)