“If you want to see what a world with built-in backdoors looks like should congress rule on the side of the FBI, look no further than Microsoft,” Bryan Clark writes for TNW.
“One of the key points to Apple’s argument — and what made the hearing necessary in the first place — is its inability to decrypt the iPhone. Knowing this, the FBI instead sought Apple’s help in modifying iOS to disable a feature that would wipe the phone after 10 failed password attempts,” Clark writes. “But, what if Apple did have a key for every encrypted iPhone? The conflict would basically hinge on Apple’s willingness to turn said key over to the authorities. This is a battle Apple could fight, but probably wouldn’t win.”
“If the case would have involved a laptop, instead of a smartphone, and Microsoft, instead of Apple, the argument would be irrelevant,” Clark writes. “According to Matthew Green, professor of cryptography at Johns Hopkins University, in a comment to The Intercept: ‘Your [Windows PC] is now only as secure as that database of keys held by Microsoft, which means it may be vulnerable to hackers, foreign governments, and people who can extort Microsoft employees.'”
“That’s the problem with backdoors; there’s no way to ensure that they only work for the intended user,” Clark writes. “At some point in the near-future, it’s likely that Microsoft will be forced to comply with a request that takes full advantage of this security hole.”
Read more in the full article – highly recommended – here.
MacDailyNews Take: Yet another reason, as if we needed any more, not to use Microsoft garbage and to fight government overreach!
SEE ALSO:
Former CIA Director: FBI wants to dictate iPhone’s operating system – March 11, 2016
Why the government is citing Aaron Burr in its fight against Apple – March 11, 2016
U.S. government takes cheap shots at Apple – March 11, 2016
U.S. government rebuts Apple claim on password reset in iPhone case – March 11, 2016
Apple: U.S. Justice Dept attempting to ‘smear’ company by taking a ‘cheap shot’ – March 10, 2016
[Thanks to MacDailyNews Reader “Dan K.” for the heads up.]