Autocrypt

Last updated

Autocrypt is a cryptographic protocol for email clients aiming to simplify key exchange and enabling encryption. [ citation needed ] Version 1.0 of the Autocrypt specification was released in December 2017 and makes no attempt to protect against MITM attacks. [1] [ non-primary source needed ] It is implemented on top of OpenPGP replacing its complex key management by fully automated exchange of cryptographic keys between peers [ citation needed ].

Contents

Method

Autocrypt-capable email clients transparently negotiate encryption capabilities and preferences and exchange keys between users alongside sending regular emails. [ citation needed ] This is done by including the key material and encryption preferences in the header of each email, which allows encrypting any message to a contact who has previously sent the user email. [ citation needed ] This information is not signed or verified in any way even if the actual message is encrypted and verified. [ citation needed ]

No support is required from email providers other than preserving and not manipulating the Autocrypt specific header fields. [ citation needed ]

When a message is encrypted to a group of receivers, keys are also automatically sent to all receivers in this group. This ensures that a reply to a message can be encrypted without any further complications or work by the user. [ citation needed ]

Security model

Autocrypt is guided by the idea of opportunistic security from RFC 7435 but implementing something much less secure than a trust on first use (TOFU) model. Encryption of messages between Autocrypt-capable clients can be enabled without further need of user interaction. [ citation needed ] Traditional OpenPGP applications should display a noticeable warning if keys are not verified either manually or by a web of trust method before use. In contrast, Autocrypt completely resigns on any kind of key verification. Key exchange is during the initial handshake and valid or invalid keys of peers may be replaced anytime later without any user interaction or verification. This makes it very easy to exchange new key(s) if a user loses access to the key but also makes the protocol much more susceptible to man-in-the-middle attacks than clean TOFU. The underlying OpenPGP implementation makes it often possible for the user to perform manual out of band key verification, however by design users are never alerted if Autocrypt changed the keys of peers. [ citation needed ]

Autocrypt tries to maximize the possible opportunities for encryption, but is not aggressive about encrypting messages at all possible opportunities. Instead, encryption is only enabled by default if all communicating parties consent, allowing users to make themselves available for encrypted communication without getting in the way of their established workflows. [2]

Man-in-the-middle attacks are not preventable in this security model, which is controversial. [3]

Any attacker who can send emails with forged sender-address can cause encryption keys to be replaced by keys of his choice and/or deliberately turn off encryption. [4]

Technical details

Autocrypt uses the established OpenPGP specification as its underlying data format. Messages are encrypted using AES and RSA keys, with a recommended RSA key length of 3072 bits. These mechanisms are chosen for maximum compatibility with existing OpenPGP implementations. There are plans for moving to smaller Elliptic-curve keys when support is more widely available. [5]

The Autocrypt header field features a tag=value format common to several mechanisms (for example dkim), where the keydata tag contains the public key. It is similar to an armored key export, except that it misses the -----BEGIN PGP PUBLIC KEY BLOCK----- and -----END PGP PUBLIC KEY BLOCK----- lines. [6]

For example:

Autocrypt:addr=alice@autocrypt.example;prefer-encrypt=mutual;keydata= mDMEXEcE6RYJKwYBBAHaRw8BAQdArjWwk3FAqyiFbFBKT4TzXcVBqPTB3gmzlC/Ub7O1u12 0F2FsaWNlQGF1dG9jcnlwdC5leGFtcGxliJYEExYIAD4WIQTrhbtfozp14V6UTmPyMVUMT0 fjjgUCXEcE6QIbAwUJA8JnAAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRDyMVUMT0fjj kqLAP9frlijwBJvA+HFnqCZcYIVxlyXzS5Gi5gMTpp37K73jgD/VbKYhkwk9iu689OYH4K 7q7LbmdeaJ+RX88Y/ad9hZwy4OARcRwTpEgorBgEEAZdVAQUBAQdAQv8GIa2rSTzgqbXCp DDYMiKRVitCsy203x3sE9+eviIDAQgHiHgEGBYIACAWIQTrhbtfozp14V6UTmPyMVUMT0fj jgUCXEcE6QIbDAAKCRDyMVUMT0fjjlnQAQDFHUs6TIcxrNTtEZFjUFm1M0PJ1Dng/cDW4xN 80fsn0QEA22Kr7VkCjeAEC08VSTeV+QFsmz55/lntWkwYWhmvOgE= 

Support

Further reading

Related Research Articles

Pretty Good Privacy (PGP) is an encryption program that provides cryptographic privacy and authentication for data communication. PGP is used for signing, encrypting, and decrypting texts, e-mails, files, directories, and whole disk partitions and to increase the security of e-mail communications. Phil Zimmermann developed PGP in 1991.

<span class="mw-page-title-main">Public-key cryptography</span> Cryptographic system with public and private keys

Public-key cryptography, or asymmetric cryptography, is the field of cryptographic systems that use pairs of related keys. Each key pair consists of a public key and a corresponding private key. Key pairs are generated with cryptographic algorithms based on mathematical problems termed one-way functions. Security of public-key cryptography depends on keeping the private key secret; the public key can be openly distributed without compromising security.

<span class="mw-page-title-main">GNU Privacy Guard</span> Complete implementation of the OpenPGP and S/MIME standards

GNU Privacy Guard is a free-software replacement for Symantec's cryptographic software suite PGP. The software is compliant with RFC 4880, the IETF standards-track specification of OpenPGP. Modern versions of PGP are interoperable with GnuPG and other OpenPGP-compliant systems. GnuPG is however expected, as of April 2024, to break compliance with the upcoming revision of OpenPGP and thus with other implementations that will continue to comply.

<span class="mw-page-title-main">Email client</span> Computer program used to access and manage a users email

An email client, email reader or, more formally, message user agent (MUA) or mail user agent is a computer program used to access and manage a user's email.

<span class="mw-page-title-main">Web of trust</span> Mechanism for authenticating cryptographic keys

In cryptography, a web of trust is a concept used in PGP, GnuPG, and other OpenPGP-compatible systems to establish the authenticity of the binding between a public key and its owner. Its decentralized trust model is an alternative to the centralized trust model of a public key infrastructure (PKI), which relies exclusively on a certificate authority. As with computer networks, there are many independent webs of trust, and any user can be a part of, and a link between, multiple webs.

Hushmail is an encrypted proprietary web-based email service offering PGP-encrypted e-mail and vanity domain service. Hushmail uses OpenPGP standards. If public encryption keys are available to both recipient and sender, Hushmail can convey authenticated, encrypted messages in both directions. For recipients for whom no public key is available, Hushmail will allow a message to be encrypted by a password and stored for pickup by the recipient, or the message can be sent in cleartext. In July 2016, the company launched an iOS app that offers end-to-end encryption and full integration with the webmail settings. The company is located in Vancouver, British Columbia, Canada.

<span class="mw-page-title-main">Enigmail</span> Extension for Mozilla Thunderbird and SeaMonkey

Enigmail is a data encryption and decryption extension for Mozilla Thunderbird and the Postbox that provides OpenPGP public key e-mail encryption and signing. Enigmail works under Microsoft Windows, Unix-like, and Mac OS X operating systems. Enigmail can operate with other mail clients compatible with PGP/MIME and inline PGP such as: Microsoft Outlook with Gpg4win package installed, Gnome Evolution, KMail, Claws Mail, Gnus, Mutt. Its cryptographic functionality is handled by GNU Privacy Guard.

<span class="mw-page-title-main">Key exchange</span> Cryptographic method

Key exchange is a method in cryptography by which cryptographic keys are exchanged between two parties, allowing use of a cryptographic algorithm.

S/MIME is a standard for public-key encryption and signing of MIME data. S/MIME is on an IETF standards track and defined in a number of documents, most importantly RFC 8551. It was originally developed by RSA Data Security, and the original specification used the IETF MIME specification with the de facto industry standard PKCS #7 secure message format. Change control to S/MIME has since been vested in the IETF, and the specification is now layered on Cryptographic Message Syntax (CMS), an IETF specification that is identical in most respects with PKCS #7. S/MIME functionality is built into the majority of modern email software and interoperates between them. Since it is built on CMS, MIME can also hold an advanced digital signature.

Internet security is a branch of computer security. It encompasses the Internet, browser security, web site security, and network security as it applies to other applications or operating systems as a whole. Its objective is to establish rules and measures to use against attacks over the Internet. The Internet is an inherently insecure channel for information exchange, with high risk of intrusion or fraud, such as phishing, online viruses, trojans, ransomware and worms.

In cryptography and steganography, plausibly deniable encryption describes encryption techniques where the existence of an encrypted file or message is deniable in the sense that an adversary cannot prove that the plaintext data exists.

The following tables compare general and technical features of notable email client programs.

Email authentication, or validation, is a collection of techniques aimed at providing verifiable information about the origin of email messages by validating the domain ownership of any message transfer agents (MTA) who participated in transferring and possibly modifying a message.

DomainKeys Identified Mail (DKIM) is an email authentication method designed to detect forged sender addresses in email, a technique often used in phishing and email spam.

Email encryption is encryption of email messages to protect the content from being read by entities other than the intended recipients. Email encryption may also include authentication.

Invisible mail, also referred to as iMail, i-mail or Bote mail, is a method of exchanging digital messages from an author to one or more recipients in a secure and untraceable way. It is an open protocol and its java implementation (I2P-Bote) is free and open-source software, licensed under the GPLv3.

<span class="mw-page-title-main">Proton Mail</span> End-to-end encrypted email service

Proton Mail is a Swiss end-to-end encrypted email service founded in 2013 headquartered in Plan-les-Ouates, Switzerland. It uses client-side encryption to protect email content and user data before they are sent to Proton Mail servers, unlike other common email providers such as Gmail and Outlook.com. The service can be accessed through a webmail client, the Tor network, Windows, macOS and Linux (beta) desktop apps and iOS and Android apps.

<span class="mw-page-title-main">Mailvelope</span> Browser extension for OpenPGP encryption with webmail services

Mailvelope is free software for end-to-end encryption of email traffic inside of a web browser that integrates itself into existing webmail applications. It can be used to encrypt and sign electronic messages, including attached files, without the use of a separate, native email client using the OpenPGP standard.

<span class="mw-page-title-main">Mailfence</span> Encrypted email service

Mailfence is secure encrypted email service that offers OpenPGP based end-to-end encryption and digital signatures. It was launched in November 2013 by Belgium-based company ContactOffice Group that has been operating an online collaboration suite since 1999.

<span class="mw-page-title-main">OpenKeychain</span>

OpenKeychain is a free and open-source mobile app for the Android operating system that provides strong, user-based encryption which is compatible with the OpenPGP standard. This allows users to encrypt, decrypt, sign, and verify signatures for text, emails, and files. The app allows the user to store the public keys of other users with whom they interact, and to encrypt files such that only a specified user can decrypt them. In the same manner, if a file is received from another user and its public keys are saved, the receiver can verify the authenticity of that file and decrypt it if necessary. As of August 2021, it is no longer actively developed.

References

  1. "Autocrypt FAQ". autocrypt.org. Retrieved 8 December 2019.
  2. "OpenPGP Considerations, Part III: Autocrypt and Encryption by Default | K-9 Mail". k9mail.github.io. Retrieved 28 April 2018.
  3. "Bye-bye Enigmail!: OpenPGP wird in Thunderbird integriert - Golem.de". www.golem.de (in German). Retrieved 23 December 2019.
  4. "Autocrypt FAQ — What about spammers accidentally downgrading encryption?". autocrypt.org. Retrieved 1 December 2019.
  5. "Autocrypt FAQ — Why RSA3072 and 25519 only later?". autocrypt.org. Retrieved 29 April 2018.
  6. "The Autocrypt Header". autocrypt.org. Retrieved 29 May 2024.
  7. Paul Brown, Carl Schwan, and Áron Kovács (22 April 2021). "KDE Gear 21.04 released" . Retrieved 22 April 2021.{{cite web}}: CS1 maint: multiple names: authors list (link)
  8. "Delta Chat v0.9.2 feat. Autocrypt Level 1" . Retrieved 26 April 2018.
  9. "5.4 Release | K-9 Mail". Archived from the original on 21 December 2018. Retrieved 24 April 2018.
  10. "K-9 mail fails to encrypt emails by default, even with "Autocrypt mutual mode" enabled". GitHub . Retrieved 27 February 2021.
  11. "Releases: the-djmaze/snappymail". GitHub . Retrieved 17 February 2024.
  12. "Does Thunderbird support Autocrypt?". Mozilla Support. 26 June 2022. Retrieved 25 June 2024.
  13. "Vereinfachte E-Mail-Verschlüsselung mit Autocrypt- und OpenPGP-Header". Posteo.de (in German). 18 December 2017. Retrieved 24 April 2018. [Our contribution to security: We additionally secure the key exchange with Autocrypt with digital signatures (DKIM). This is not currently provided as standard with Autocrypt. Our provider-side DKIM signature ensures that public keys cannot be manipulated unnoticed during transport. We also sign Autocrypt headers that your local email program may add with DKIM. The signature is applied if the sender matches the mailbox. We save the key exchange with Autocrypt additionally with digital signatures (DKIM). This is not yet provided by default at Autocrypt. Our provider-side DKIM signing ensures that public keys cannot be manipulated unnoticed on transport. We also sign autocrypt header, which your local email program may add, with DKIM. The signature is made when the sender matches the mailbox.]
  14. "Autocrypt". addons.thunderbird.net. Retrieved 8 October 2019.
  15. Patrick Brunschwig. "Enigmail - 2018-03-25 Enigmail v2.0 released" . Retrieved 24 April 2018.
  16. Bertram, Linda A.; Dooble, Gunther van (31 July 2019). Transformation of Cryptography: Fundamental concepts of Encryption, Milestones, Mega-Trends and sustainable Change in regard to Secret Communications and its Nomenclatura. BoD – Books on Demand. ISBN   978-3-7494-5074-9.
  17. Gasakis, Mele; Schmidt, Max (8 January 2019). The New Era Of Exponential Encryption: - Beyond Cryptographic Routing with the Echo Protocol [Paperback]. BoD – Books on Demand. ISBN   978-3-7481-5886-8.