News for hackers. Stuff that matters.
Re:Apple’s approach to privacy by subliminalpanda on Tuesday September 29, 2015 @11:51AM (#10297166)
I was reading their guidelines for law enforcement requests: https://www.apple.com/privacy/docs/emeia_le_guidelines_final...

Interesting note: "P. FaceTime FaceTime communications are end-to-end encrypted and Apple has no way to decrypt FaceTime data when it is in transit between devices. Apple cannot intercept FaceTime communications. Apple has FaceTime call invitation logs when a FaceTime call invitation is initiated. These logs do not indicate that any communication between users actually took place. Apple has no information as to whether the FaceTime call was successfully established or duration of a FaceTime call. FaceTime call invitation logs are retained up to 30 days. FaceTime call invitation logs are available only following receipt of a legally valid request"

iMessage is not mentioned. Does this mean they are capable of intercepting iMessage?

edit: in the FAQ it says "Can Apple intercept users’ communications pursuant to a Wiretap Order? Apple can intercept users’ email communications, upon receipt of a valid Wiretap Order. Apple cannot intercept users’ iMessage or FaceTime communications as these communications are end-to-end encrypted."

Re:Apple’s approach to privacy by Jerry2 on Tuesday September 29, 2015 @12:03PM (#10297253)
>Does this mean they are capable of intercepting iMessage?

You know what the best way is to see who cooperates with law enforcement and to what level? Court documents!

I've been trawling court documents for the past few months (I'm writing a blog article on this) and I'm yet to find iMessage being used in court (unless the access to the conversation was given by one of the parties). iMessage really does seem secure from legal system point of view.

For a comparison, I've found dozens of court documents from Google, Facebook, Microsoft handing over chat logs from Hangouts, Whatsapp/FBMessenger, Skype.

Anyway, if you want to see the level of cooperation and want to double-check privacy policies, actual court documents are the best way.

Re:Apple’s approach to privacy by cryptophreak on Tuesday September 29, 2015 @12:14PM (#10297332)
“Parallel construction is a law enforcement process of building a parallel - or separate - evidentiary basis for a criminal investigation in order to conceal how the investigation actually began.”

https://en.wikipedia.org/wiki/Parallel_construction

Re:Apple’s approach to privacy by frandroid on Tuesday September 29, 2015 @12:35PM (#10297488)
Police use parallel construction when they don't want to reveal their methods. I seriously doubt law enforcement would engage in parallel construction if it had access to iMessage but Apple asked it to.
Re:Apple’s approach to privacy by MacsHeadroom on Tuesday September 29, 2015 @04:23PM (#10299348)
> I seriously doubt law enforcement would engage in parallel construction if it had access to iMessage but Apple asked it to.

Why? They've been using parallel construction to avoid violating NDAs and giving up their capabilities for years. http://www.wired.com/2014/03/harris-stingray-nda/

Re:Apple’s approach to privacy by frandroid on Tuesday September 29, 2015 @05:46PM (#10299953)
That's exactly the case I was thinking about with my comment

1) Police don't care that APPLE doesn't want to reveal its methods, and 2) Unlike the Stingray, it wouldn't be illegal for them to use iMessage evidence in court if Apple provided it to them (especially with the use of a warrant!)

Re:Apple’s approach to privacy by haldean on Tuesday September 29, 2015 @06:21PM (#10300210)
I think it's more about the police not wanting the public to know that iMessage is owned; having trusted-but-broken communication services is a serious advantage for them.
Re:Apple’s approach to privacy by teekert on Tuesday September 29, 2015 @12:19PM (#10297377)
I'm also looking forward to your post. Whatsapp is supposed to be end-to-end encrypted with messages only stored on the phone, at least it has reportedly been like that since end of 2014. It would be extremely interesting and a big scandal if you found documents with Whatsapp messages in them dating from 2015.
Re:Apple’s approach to privacy by subliminalpanda on Tuesday September 29, 2015 @12:43PM (#10297549)
Only from android to android. Other platforms don't have it implemented yet.
Re:Apple’s approach to privacy by athrun on Tuesday September 29, 2015 @12:09PM (#10297297)
Sounds very interesting! I will be waiting for the blog post :)
Re:Apple’s approach to privacy by subliminalpanda on Tuesday September 29, 2015 @12:44PM (#10297553)
May I have a link to your blog?
Re:Apple’s approach to privacy by devcpp on Tuesday September 29, 2015 @03:55PM (#10299123)
Secret courts.
Re:Apple’s approach to privacy by gambiter on Wednesday September 30, 2015 @08:23AM (#10303358)
Ok... So, why would Apple receive the benefit of only exposing iMessage data in secret courts when Google, Facebook, and Microsoft all have to do it in open court documents?
Re:Apple’s approach to privacy by r00fus on Tuesday September 29, 2015 @01:20PM (#10297808)
Knowing that most phone lines are essentially considered tapped by the NSA/FBI...

So is privacy a good reason to use FaceTime Audio over say, a standard voice call?

Re:Apple’s approach to privacy by Synaesthesia on Tuesday September 29, 2015 @05:26PM (#10299765)
I'd say yes, it's a lot harder to tap into than a cell phone call.
Re:Apple’s approach to privacy by kenferry on Tuesday September 29, 2015 @01:02PM (#10297663)
iMessage is discussed in great detail in https://www.apple.com/business/docs/iOS_Security_Guide.pdf
Re:Apple’s approach to privacy by tomschlick on Tuesday September 29, 2015 @03:46PM (#10299045)
Most relevant excerpt (page 34):

How iMessage sends and receives messages

Users start a new iMessage conversation by entering an address or name. If they enter a phone number or email address, the device contacts the IDS to retrieve the public keys and APNs addresses for all of the devices associated with the addressee. If the user enters a name, the device first utilizes the user’s Contacts app to gather the phone numbers and email addresses associated with that name, then gets the public keys and APNs addresses from the IDS.

The user’s outgoing message is individually encrypted for each of the receiver’s devices. The public RSA encryption keys of the receiving devices are retrieved from IDS. For each receiving device, the sending device generates a random 128-bit key and encrypts the message with it using AES in CTR mode. This per-message AES key is encrypted using RSA-OAEP to the public key of the receiving device. The combination of the encrypted message text and the encrypted message key is then hashed with SHA-1, and the hash is signed with ECDSA using the sending device’s private signing key. The resulting messages, one for each receiving device, consist of the encrypted message text, the encrypted message key, and the sender’s digital signature. They are then dispatched to the APNs for delivery. Metadata, such as the timestamp and APNs routing information, is not encrypted. Communication with APNs is encrypted using a forward-secret TLS channel.