Hector Martin

As you can see in the last line, you get a very clear message. "WARNING: Message was not integrity protected." After that, it's up to your email client to do the right thing. 5/

Your email client should refuse to render the message. If it ignores the warning or does the wrong thing in response to it, then yes, the Efail attack is very real. So it's really more fair to say this is an attack on poorly-written clients, not OpenPGP. 6/

The OpenPGP spec does technically allow for non-MDCed messages. It has to for backwards compatibility reasons. But no modern OpenPGP client should silently ignore missing/malformed MDCs. No modern email client should ignore the OpenPGP client's warnings. 7/

GnuPG has given warnings on missing/malformed MDCs for years. And although the Efail authors did find some problems in Enigmail -- for which we're deeply sorry, and plead that we're only human -- we fixed them months ago. 8/

If you're using a recent GnuPG and Enigmail 2.0 or later, you should be fine. If you're not, consider this an object lesson in the importance of upgrading your security-critical software. 9/

Is 2.0.0 the threshold version for the fix? I see a bunch of security fixes went into 1.9.9, but I'm not sure if it's one of those or this was fixed later (Gentoo has 1.9.9 as stable and I'm trying to figure out if I need to file a security stablereq). https://bugs.gentoo.org/643490