Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Some metadata and usage information stored in iCloud remains under standard data protection, even when Advanced Data Protection is enabled. For example, dates and times when a file or object was modified are used to sort your information, and checksums of file and photo data are used to help Apple de-duplicate and optimize your iCloud and device storage — all without having access to the files and photos themselves.

> • iCloud Drive The raw byte checksums of the file content and the file name

> • Photos The raw byte checksum of the photo or video

https://support.apple.com/en-us/HT202303



That means that you’re not safe to store known files your local dictator doesn’t like, isn’t it? Wouldn’t a sort of per-user salt allow the same functionality and give more confidentially?


Can someone say more on this point?

If there is a "Revolution Plan (WIP)" document shared amongst a few agitators, and someone in power gets their hand on it (and its "checksum" or whatever), then can they figure out _who else_ has it?


More or less, yes. Apple could search for a list of iCloud users with that hash in their account and single them out without breaking the encryption (not that they can't do that too).


It wouldn't allow them to deduplicate across users, which they are likely doing.

When you send your group iMessage of 30 people the same photo, apple is not storing 30 copies of it, but, one.


Is that actually true?

My understanding of how E2E encrypted iMessage works is that in group chats it does indeed send 30 copies of your messages, individual encrypted for each recipient in the group.

https://support.apple.com/en-gb/guide/security/sec70e68c949/...

> For group conversations, this process is repeated for each recipient and their devices.


Perhaps they're doing multi-recipient encryption, ie. the data is wrapped with one key, and that private key is then encrypted with the public key of each recipient, so everyone ends up using the same private key to decrypt the file data itself. This means the actual file data isn't sent 20+ times (although the data is indeed stored in everyone's Messages backups separately; if Apple is doing de-dupe based on file data+filename, they're probably benefiting from deduping group message images).


> APNs can only relay messages up to 4 or 16KB in size, depending on the iOS or iPadOS version. If the message text is too long or if an attachment such as a photo is included, the attachment is encrypted using AES in CTR mode with a randomly generated 256-bit key and uploaded to iCloud.

Only the attachment encryption key and URL need to be encrypted to each recipient.


That would be a terrible idea.

If everyone is using the same file on iCloud, then by definition the file must be encrypted with the same E2E encryption key.

That seems ripe for buggy disaster, and is a big loss of privacy. With enough phones, you could decrypt a large percentage of other peoples data.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: