3 ms·
To protect in-flight data HTTPS encryption would be sufficient, since the attacker would have to MITM the connection and forge certificates instead of passively
by the8472 12y ago
To protect in-flight data HTTPS encryption would be sufficient, since the attacker would have to MITM the connection and forge certificates instead of passively listening.
But once it reaches the end device it is impossible for snapshat to deliver on its promises of ephemeral messaging.
To display the data the device needs to be able to decrypt it. If it can be decrypted it can be copied.
It's very much the same conceptual impossibility that DRM faces.
So in the end it doesn't really matter whether it's ECB or something better. It remains a DRM scheme.
- waxjar 12y agoWas this relevant to the comment you replied to?
- the8472 12y agoYes, the point is that whether they use ECB or not makes no difference and thus can't be considered an "Oops" in this use-case. ROT13, AES-ECB or some state-of-the-art crypto, it's all the same if the end-device needs to have the key to decrypt it anyway.