I would like to suggest to add following configure option: --enable-autocrypt See attached patch. cheers arsen
Dear package maintainers, autocrypt is a cryptographic protocol for email clients aiming to simplify key exchange and enabling encryption on basis of OpenPGP and due to the fact that WoT (Web of Trust) is broken [0] since June 2019 [1] (Daniel Kahn Gillmor (dkg)) it's a needed feature. These MUAs (Mail User Agents) support autocrypt already: Thunderbird, Mailpile, Delta Chat Messenger, K-9 Mail and Mutt. Please consider my patch. cheers, Arsen [0] https://lwn.net/Articles/792366/ [1] https://dkg.fifthhorseman.net/blog/openpgp-certificate-flooding.html
Hello, I second that. Bye, Joerg
Imho this "feature" promotes a very unsafe key exchange method where an attacker can easily exchange trusted and verified keys by any keys he likes. Thunderbird support has been dropped although it does support some kind of key exchange that is in some aspect "compatible" with autocrypt. Last time I looked K9 mail had bigger problems than autocrypt support. This is even more broken than the problem it tries to solve and a waste of electrons.
I agree that --enable-autocrypt should be applied in debian's mutt package. Autocrypt may not be as secure as traditional OpenPGP fingerprint verification, but on the other hand, almost no one actually does OpenPGP fingerprint verification. And autocrypt doesn't stop people from doing fingerprint verification who want to do it. The realistic alternative to using autocrypt at scale is basically annoying and error-prone manual OpenPGP certificate distribution, which is decidedly not great. Enabling it in mutt as proposed here probably also means adding a build-dependency on libsqlite3-dev, by the way. Please do --enable-autocrypt in mutt.
I've just offered https://salsa.debian.org/mutt-team/mutt/-/merge_requests/7 as a simple fix for https://bugs.debian.org/969324 (enabling autocrypt for mutt users). Please let me know if there's anything else i can do to move this along!