Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by martyb on Wednesday January 22 2020, @02:28AM   Printer-friendly
from the all-your-data-are-belong-to-us dept.

Two years ago, Apple dropped a plan that would have made it impossible for the company to decrypt iPhone and iPad backups for law enforcement, according to a Reuters report today. Reuters wrote that "six sources familiar with the matter" confirmed that Apple dropped the end-to-end encryption plan for iCloud Backup "after the FBI complained that the move would harm investigations."

[...] "Under that plan, primarily designed to thwart hackers, Apple would no longer have a key to unlock the encrypted data, meaning it would not be able to turn material over to authorities in a readable form even under court order," the report continued.

[...] Apple had "10 or so experts" working on the end-to-end encryption plan, "variously code-named Plesio and KeyDrop," but told them to stop work on the project once the decision was made, according to Reuters' sources.

[...] Messages is a special case. Messages itself has end-to-end encryption, but iCloud Backup "includes a copy of the key protecting your Messages." If you want full protection for Messages, you'd want to disable iCloud Backup and back your iOS devices up to iTunes on your computer instead.

iCloud Backup's inclusion of a copy of the Messages key "ensures you can recover your Messages if you lose access to iCloud Keychain and your trusted devices," Apple explains. "When you turn off iCloud Backup, a new key is generated on your device to protect future messages and isn't stored by Apple."

[...] President Trump blasted Apple on Twitter last week, writing that Apple "refuse[s] to unlock phones used by killers, drug dealers and other violent criminal elements."

Apple countered that it gave the FBI "gigabytes of information" including "iCloud backups, account information and transactional data for multiple accounts."

Apple may be unable to unlock the phones since it hasn't granted the government's request for a backdoor—and continues to argue that encryption backdoors would harm security for all users.

https://arstechnica.com/tech-policy/2020/01/apple-reportedly-nixed-plan-for-end-to-end-encryption-in


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Interesting) by jmichaelhudsondotnet on Wednesday January 22 2020, @01:32PM

    by jmichaelhudsondotnet (8122) on Wednesday January 22 2020, @01:32PM (#946815) Journal

    Always 'apple changed their minds about privacy and didn't implement feature X'

    Apple empowered the totalitarian state, obeyed government authority wishes, lied about privacy to their customers and users, gave them a sense of privacy without any actual privacy, and provides phones that are outright extensions of the police station. Every conversation you have on these devices is as if you were in an interrogation room with a false mirror.

    These are all patterns of imposed socialism, fiat socialism, command socialism, dictatorial socialism, corporate socialism, but it is national socialism, also known as nazi policies. From apple. You know the one that in 1984 had the commercial about bringing color to a black and white dystopia...From grand ideal of freedom, to just another brick in the wall in, 35 years.

    Sigh. Garbage people and their garbage claim another set of ideas for their junkpile.

    thesesystemsarefailing.net
    (side topic, what would you do if you typed an ssh command into the built in terminal on a recent macbook and when the command failed, the history does not match what you entered? And you confirm 5 times, extra characters get added to the username everytime. ssh user@domain.net became ssh uuuuser@domain.net in the command history. Then uuubusser@domain.net, then ussser@domain.net, and every time when you hit enter it looked like 'user@domain.net'. What could cause that? How would you investigate? Sadly I no longer have the machine it was a loner for a day.)

    Starting Score:    1  point
    Moderation   +2  
       Interesting=1, Underrated=1, Total=2
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4