Sunday, 20 October 2013

Apple Says iMessage Interception Would Require Re-Engineering Systems, Has No Interest in Doing So


ios_7_messages_icon 
Yesterday, researchers made a presentation at the Hack in the Box conference arguing that Apple's iMessage system could theoretically allow Apple or another party to intercept the encrypted messages. The concern stems in part from Apple's use of a private server for storing users' public keys used to encrypt messages, meaning that senders have no way of knowing whether a potentially false key has been inserted in order to intercept messages intended for a different recipient.
In a statement to AllThingsD, Apple once again denies that it can read iMessages, noting that it would require the service's systems to be re-engineered and that the company has no interest in doing so.

Apple says that QuarksLab’s theory is just that — a theory, and one that would require a rearchitecting of iMessage for it ever to be a threat in the real world.
“iMessage is not architected to allow Apple to read messages,” said Apple spokeswoman Trudy Muller said in a statement to AllThingsD. “The research discussed theoretical vulnerabilities that would require Apple to re-engineer the iMessage system to exploit it, and Apple has no plans or intentions to do so.”
Apple's statement does not actually refute the original claim, simply confirming that as the service is currently configured it is impossible for Apple to intercept iMessages. The researchers' argument rests on the observation that changes could be made to Apple's systems to allow for iMessages to be intercepted without users being aware of the changes.

The result is that Apple is arguing users should trust that the company has no interest in making such changes, and if users take Apple at its word, the researchers' concerns remain merely theoretical. But some users may remained concerned that Apple could be quietly compelled to make changes by government security agencies, compromising Apple's touted "secure end-to-end encryption" for iMessage.

No comments:

Post a Comment