Profile picture
Filippo Valsorda @FiloSottile
, 6 tweets, 2 min read Read on Twitter
No, in 2018 you don’t get to claim the high ground and blame users and implementations if your crypto API returns the plaintext on a decryption error.

At most you can say “sorry we are a legacy system, no one knew better then, it’s time to migrate off”.
I really don’t get the community’s negative reaction. This is a perfect case study for proper AEADs, safe APIs, and against secure email in general.
[0] days since retrofitting security on top of a complex existing system blew up.
And wait, apparently you can even strip the authentication tag outright, downgrading the decryption error to just a warning?!
The GnuPG (v2.2.7) command line tool is also happy to create the plaintext output file when the authentication tag is missing (or stripped).

Only a warning and a non-zero exit code.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Filippo Valsorda
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($3.00/month or $30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!