5 ms·
The original tweet linked in the article [1] says "They might reveal the plaintext of encrypted emails, including encrypted emails sent in the past.", so at lea
by rococode 8y ago
The original tweet linked in the article [1] says "They might reveal the plaintext of encrypted emails, including encrypted emails sent in the past.", so at least that much is probably compromised. They also say there are currently no reliable fixes, which seems to suggest the problem is a flaw in PGP's design rather than a security bug in some specific library or tool, since a simple (but widespread) bug would most likely have a clear fix.
[1] https://twitter.com/seecurity/status/995906576170053633 https://twitter.com/seecurity/status/995906576170053633
- jstanley 8y agoGood point. I wonder what kind of flaw in PGP's design could make it unsafe to decrypt incoming mails.
- skunkworker 8y agoIt'll be interesting to see the flaw that many pgp clients all seemed to implement in the same/similar ways.
- im3w1l 8y agoAt a guess: 1. Take previous email (X) that you want to decrypt. 2. Apply transformation (this is the actual secret sauce) to previous X to get email Y. 3. Because of how Y was constructed, decrypting it causes X to be decypted. 4. Phone home with the result by using some kind of tracking pixel. My reasoning is that they didn't talk about RCE and they didn't talk about stealing the key, and they did warn about automatic decryption, so it should be about tricking the decryptor into decrypting whatever you want for you.
- jstanley 8y agoUpdate: you were right :)
- jwildeboer 8y agoThey claim this also affects S/MIME, so concluding a flaw only in GPG/PGP seems to be wrong.
- giancarlostoro 8y agoIt seems more to be with the mail clients themselves given that to avoid the exploit your best best is not to render HTML emails. That is outside of the scope of goals for the encryption libraries altogether.