|
I'm pretty sure that would be illegal and any evidence uncovered would be inadmissible in any U.S. court. Law enforcement wouldn't be use any incriminating evidence, if found, to levy charges against any other accomplices.
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|
|
If Mr. Cook chooses to ignore a court order, then Mr. Cook should be held in contempt of court.
Isn't this what would happen to the rest of us?
|
|
|
|
|
Of course it would. I can't see any good reason why Apple can't unlock this one phone.
If it's not broken, fix it until it is
|
|
|
|
|
I don't think he's simply going to "ignore" the ruling, they're going to appeal the decision. I'm sure Apple has an army of lawyers.
|
|
|
|
|
at first i as reading this as Mr. Crook, not Cook.
Yeah Mr. Crook is ignoring court order.
|
|
|
|
|
Ben Franklin: Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety.
'nuff said.
There are two types of people in this world: those that pronounce GIF with a soft G, and those who do not deserve to speak words, ever.
|
|
|
|
|
He said that right before he discovered electricity and changed the world.
If it's not broken, fix it until it is
|
|
|
|
|
There are two types of people in this world: those that pronounce GIF with a soft G, and those who do not deserve to speak words, ever.
|
|
|
|
|
We're supposed to be the home of the brave, not the home of the pansies. +5 million
Jeremy Falcon
|
|
|
|
|
Yup. I read a book about 1984... things were really screwed up back then. Hope it doesn't happen again.
Mark
Just another cog in the wheel
|
|
|
|
|
I see a couple of problems with your argument:
1. Apple at the moment can claim that an attempt to unlock the phone constitutes an "undue burden" - cracking the encryption on the account is presumably non-trivial. Once it has been done, however, the FBI has both precedent and the existence of the cracking tool on its side. How long do you think it will be before they persuade judges to give them court orders for all (not just terrorist) cases?
2. Once the unlocking tool has been developed, do you really believe it will remain only in the hands of the "Good Guys"? I would not bet anything I care to lose that the tool won't be in the hands of the criminal fraternity by the end of the month. Given that Apple's encryption protects sensitive financial data, among other things, the consequences are not good.
I agree that a good look at the terrorist's phone might provide important clues, but some benefits are not worth the future cost.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
If such a tool existed - and I was a Serious Criminal - I'd be prepared to spend BIG money in terms of bribes to the appropriate Apple employee(s) to get a copy of the source.
How many people here would turn down - say - ten years salary in a Swiss bank account? The criminals could get that back in a day...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Having been a developer for 30+ years, I can't sit here and believe that Apple doesn't already have a way to open a phone.
Have you ever written encryption without a way to unlock it? How would you test it without an unlocking mechanism?
It already exists - Apple just doesn't want to give it up.
If it's not broken, fix it until it is
|
|
|
|
|
A good encryption system is one that will not allow an attacker to decrypt a ciphertext even if he (a) knows the encryption/decryption algorithms and (b) has both plaintext and ciphertext of a set of messages encrypted with the key. If the key used has enough bits, the only way to crack the encryption is to attack the algorithm.
Once the algorithm is known to be sound, you test an encryption system by generating keys (or key pairs). You do not encrypt (and destroy the plaintext) of any important data.
No one can prove that many popular algorithms do not have built-in "back doors" (rumors about the NSA's work are legion), but if so - no one is talking...
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Daniel Pfeffer wrote: No one can prove that many popular algorithms do not have built-in "back doors"
Most widely used algorithms have open-source implementations, meaning you can look at the source and see if you see any deficiencies or back doors. So... the algorithms themselves are pretty sound.
|
|
|
|
|
Very few people have the background in cryptography required to analyze an encryption algorithm. An algorithm with a vulnerability could be perfectly encoded, but still be vulnerable to attack.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
"Very few" is different than "no one", I believe you used the latter.
Daniel Pfeffer wrote: An algorithm with a vulnerability could be perfectly encoded, but still be vulnerable to attack.
Sure, that is true of anything in this world, but that's the rationale for open sourcing projects... To allow other people other than the original designers to assess vulnerabilities.
|
|
|
|
|
Once you let the Genie out of the bottle, you can't put it back in...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
This section seems a bit strange:-
Quote: Specifically, the FBI wants us to make a new version of the iPhone operating system, circumventing several important security features, and install it on an iPhone recovered during the investigation. In the wrong hands, this software — which does not exist today — would have the potential to unlock any iPhone in someone's physical possession.
If the file exists on the phone and was encrypted using an existing version of the data, how would installing a new version of the iOS allow easier unencryption?
Also - wouldn't doing that utterly corrupt the chain of evidence meaning anything discovered could not possibly be used in a civilian court of law?
|
|
|
|
|
No
Yes
If it's not broken, fix it until it is
|
|
|
|
|
They have enough evidence to go to any level of legal measure required. This is an attempt to get more information and intelligence.
|
|
|
|
|
I believe I read somewhere that there's currently a security measure that deletes the encryption key upon too many failed attempted login attempts. If I'm not mistaken, they're asking Apple to change that setting so that they can brute force the password (i.e. make it so it doesn't delete anything when faced with a brute force attack).
|
|
|
|
|
Duncan Edwards Jones wrote: If the file exists on the phone and was encrypted using an existing version of the data, how would installing a new version of the iOS allow easier unencryption?
My understanding is that if you attempt bad passwords X number of times, the phone bricks itself essentially. The "new" iOS being requested by the courts/FBI would allow unlimited attempts therefore making any phone that can have that OS installed brute forcible.
|
|
|
|
|
We answered the same thing at just about the same time, so I guess that is the stated story.
I can see the concern, if this "modified" version of the OS got out onto "the wild", anybody could brute force an iPhone.
|
|
|
|
|
Vark111 wrote:
My understanding is that if you attempt bad passwords X number of times, the phone bricks itself essentially. The "new" iOS being requested by the courts/FBI would allow unlimited attempts therefore making any phone that can have that OS installed brute forcible. Ten attempts. Then the phone not just blocks all info on the phone, it erases it completely. After that no tool can recover it; there is nothing to recover.
The code in question is a 4 decimal digit code, so a brute force attack requires only ten thousand tries (or on the average half of that) - so little that it neither sounds very much "brute" nor very strong "force"
|
|
|
|