545 karma · joined January 27, 2012
What you describe is not what's being asked for. What the FBI wants is a tool to get into this phone. They will definitely want to get into more phones in the future, but that's not the same as a single tool that gets into any phone. It can be a new one every time. If it wasn't possible to make such a tool, I'd be a lot more outraged. But it is. Tell me why that can't be done.
It would be neat if the supreme Court would say this is unconstitutional on some ground, because that would seem to apply to other forms of wiretapping. They aren't fundamentally different. I'm sure the first time the gov asked a company to help them install wire taps, it seemed like a big deal.
I think some people are being intellectually dishonest when they say a backdoor can't be created without sacrificing security for everyone else. It can be done such that your privacy on an iPhone is just as good after a backdoor is created as it was before. Which is to say, not perfect because Apple had the key either way. If you want real security use a good passcode and keep it in your head.
I mean, why draw the line here? Bugs and taps were new at one point. Why not say "police used to get things done without these newfangled spy devices, so why should we allow it now?" I would say a bug or tap is actually very invasive, but as long as a warrant is required, it doesn't seem so bad.
Let's debate honestly about what we think is acceptable. I honestly don't know, but I think perfect security is a mathematical inevitability, so I guess I'm more on the side of figuring out how to live with it.
Or everyone who disagrees with you is dumb or a shill. Sounds like real sound reasoning.
This sounds like a misunderstanding. No clever third parties are going to find a way to break code signing. To exploit the security hole Apple already created would require having Apple's signing certificate so that a phone could install the code. If it wasn't for the certificate, it would be quite a bit more trivial to hack a firmware to do a malicious thing and install it on any phone.
Not everyone will agree with you, even if you use itty bitty words they can understand. I understand the issue, even when explained in grown up words. And I don't agree.
In this case, Apple already was not "keeping good security practices in place" because they made a weak system. If they had actually made a phone that kept good security practices in place, it wouldn't be possible for them to help the FBI.
They should comply with this and then fix their crap. Then you can worry about explaining the importance of fighting any law that would undermine strong security.
Additionally, that letter is written with very carefully fuzzy language so as to remain true-ish.
As in, Apple can't make this change and guarantee that nobody else will use it. In the same way that any software change (which they do regularly) could open up a security flaw. That doesn't mean it's likely, or any more likely than any other software update.
And it should be pointed out that point A never existed. Apple's device is not fully secure, or they wouldn't be capable of complying with the FBI.
And to your last point: this software is not secure. That's why we have this backdoor option.
I don't know. It seems like that is the way the law works now. If it's not what we want, maybe that should be the discussion. But this doesn't seem fundamentally different than any other normal search order. Superficially different, sure. Instead of simply unlocking a door, it's more like Apple has the blueprints for how to make a key and they're being asked to do so. Apple is implying (but strangely, not explicitly saying) that they can't do that without harming security for other people. I don't believe it, or they should come out and say that.
And lastly, I think it's splitting hairs to complain that they're being asked to write special software rather than just hand over documents or unlock a door. To a lay person that may seem like an over burden, but for SMEs it should be pretty easy. If it isn't easy, again, that should be what Apple says, but they haven't. Because it's embarrassing for them.
The position Apple should be in, is to say "we cannot comply with this request". That would be great. But they can, pretty easily I would guess, so they're beating around the bush instead.
No, you appear to be purposely taking my words out of context.
I said the government should not be trusted with a carte blanch skeleton key to access any phone.
Then you said I'm trusting the government not to get access to Apple's signing keys. Which of course I trust, and which you do too. If the government could get Apple's keys, they could just make their own firmware change, sign it, and install it on any phone they want. They wouldn't need this case.
> No I'm not. The keys will be acquired when necessary, if they haven't already.
Now that is some tin foil hattery. That would be reason for outcry. It's a big leap from where we are now.
If this case sets a precedent in either direction (pro or anti privacy), then the battle is already lost because nobody understands what's going on. This is in no way the same as the government circumventing privacy. If people don't understand that, then they're not going to understand a more principled argument of a company impeding a perfectly legal request to get access to the data on a phone.
Is your problem that you don't like the ability of the government to get and execute a search warrant against a person? You don't think they should be able to? If they can search your property, and they can demand for example that your landlord grant physical access, then I see no problem with this request. The responsibility is Apple's to make it so the phone can't be unlocked by Apple.
Drawing the line at software is arbitrary and does a disservice. It's that same narrow minded view of software (as being somehow different than the physical world) that leads to idiotic things like treating email inboxes different than physical inboxes.
Edit: oh, I see what you mean. The single =. But it's pseudocode. That happens to look a lot like Javascript with a bug :)