4 ms·
> no mass-market computing platform has been safer than the flagship hardware/software platforms from Apple and Google That's a pretty low bar, because, as you
by lisper 8y ago
> no mass-market computing platform has been safer than the flagship hardware/software platforms from Apple and Google
That's a pretty low bar, because, as you say:
> SS7 is insecure
Also...
> operational practices at both the carriers and inside governments rely on those insecurities to get jobs done, and some of those jobs are important and enjoy wide support
Sure, law enforcement is easier then the citizenry isn't free. But the U.S. used to pride itself on being the one place on earth where that argument does not carry the day.
- tptacek 8y agoI'm sorry, Ron, but this is a non-sequitur. The premise of my argument is that SS7 is insecure, and that doesn't matter, because modern phones don't rely on SS7 as a secure channel.
- lisper 8y agoThey do if you are making a regular phone call. But (and you and I have been down this road several times now) even if you are not using the baseband you have only apple’s word that the rest is secure. No one outside apple can audit their products.
- tptacek 8y agoThat's pretty obviously hyperbolic, since Apple's OS and firmware code is one of the two most aggressively reverse-engineered codebases in the industry.
- lisper 8y agoiOS 12.1.2 is 1.6 GB. If you could reverse-engineer it at the rate of one byte per second (which I think is wildly optimistic) it would take you 50 years to get through the whole thing. So no, I don't think it's "wildly hyperbolic" to suggest that Apple could hide a backdoor in there somewhere if they wanted to.
- wglb 8y agoWhere in the world did you get one byte per second?? Perhaps give it a try yourself?
- lisper 8y agoI pulled it out of my hat. What do you think is a realistic rate for reverse-engineering machine code?
- pvg 8y agoA lot more seems to be pulled out of a hat here, though. At how many bytes per second do you read and interpret regular high-level source code? How do we know there isn't a secret backdoor in the Linux kernel and all of its drivers? 1.6 GB is the total image size - it's not all code, let alone OS or security-critical code. It's not all reversed from scratch every time a new update appears. It's not like the people looking at it are also staring at reams of ARM assembly. Etc, etc.
- lisper 8y ago> At how many bytes per second do you read and interpret regular high-level source code? I don't know, but it's not hard to put an upper bound on it. A VT-100 screen worth of code is at most 2000 characters. If it takes me one minute to grok the code on a screen that's (again, at most) 33 characters per second. Even if we take this upper bound as the rate at which one can process object code (which, again, seems wildly optimistic to me) that's still several work-years to go through the iOS image. > How do we know there isn't a secret backdoor in the Linux kernel and all of its drivers? We don't. I don't claim that Linux is better. Go back and look at the context of my original comment. It applies to both iOS and Android. Tptacek's response veered the discussion onto iOS. The problem is not that Apple or Google is evil or incompetent. They may be, but that's not the point. The problem is that these systems are too complicated, and the rewards for breaking them are too high. A back door in to iOS or Android could literally allow someone to rule the world (the President of the United States has been reported to use an unsecured phone). That is not a situation about which it is wise to be complacent. > 1.6 GB is the total image size - it's not all code, let alone OS or security-critical code. That is certainly true. But a back door can hide just about anywhere, so you have to look at all of it. > It's not like the people looking at it are also staring at reams of ARM assembly. Etc, etc. Yes, I know that. That's not really the point. Even if it were feasible to thoroughly audit the object code (I don't believe it is, but I'll concede it for the sake of argument) this effort is not a coordinated white-hat endeavor. Many of the reverse-engineers are black hats, or state actors not necessarily sympathetic to the needs of U.S. consumers. Even if they do find an issue it is not a slam-dunk that they will responsibly disclose it rather than attempt to exploit it for monetary or political profit.