Campaign to have end to end encryption for email by default
This would give us better privacy by hiding our emails from providers and indirectly governments getting access to our emails via these providers.
Earlier manually setting up end to end encryption with gpg was a difficult process. Now email services like Proton, Tuta and recently started Astermail have made it very easy.
Thunderbird email client has also gained gpg support without any extensions. All we need to do is ask people to encrypt emails by default. The more people can receive encrypted emails the better privacy everyone has.
I think we should start a campaign and have at least all fsci active members being able to send and receive encrypted email.
If you have a Proton, Tuta or Aster mail account then you are already covered. Just make sure to publish keys in the settings.
This would be a good time to consider switching from gmail/yahoo/outlook etc. If you want community run email servers, riseup.net and disroot.org are good. It is sad to see inventati.org shutting down.
Ravi DwivediSat 12 Sep 2026 7:28PM
I am doing this for years. Thanks to@Pirate Praveen, who taught me this 5 years ago. I use Thunderbird to encrypt and decrypt my emails.
NemoSat 12 Sep 2026 7:28PM
I have PGP configured, but don't prefer using it, since reading encrypted mails requires my Yubikey (with a touch policy) on every email read. I also don't like having a long-lived key. I instead publish a signed version of my contact preferences, asking people to reach out on Signal for any confidential communications.
Buster KeatonSat 12 Sep 2026 7:28PM
I am facing error publishing keys from Kleopatra to the server, but once it happens I am onboard.
Pirate PraveenSun 13 Sep 2026 2:17PM
@Badri Sunderarajan that sounds like a good start. I think we should arrange them in a scale explicitly with estimated difficulty level. Proton also support bridges in paid plans - same as aster https://proton.me/support/imap-smtp-and-pop3-setup
Does tuta support bridges in free plan too? I suggest setting a deadline for comments and publishing it at that point. Keeping things open ended will usually just drag on forever.
Life is TetrisSun 13 Sep 2026 5:03PM
Could we try to see if as-is e-mail accounts with Delta Chat as the client (with keys managed internally) can do an encrypted round-trip to an account with a GPG key? Or see how to make it work? It could be the solution for all those who don't manage their own keys.
Badri SunderarajanMon 14 Sep 2026 12:06PM
I wonder if it's worth having a webapp that does GPG encryption (like Mailvelope) but with keys stored password-protected on the server (like Aster/Tuta/Proton), connects to your existing Gmail/Outlook account, and tries to automatically fetch keys from keys.openpgp.org (with a warning otherwise about emails not being encrypted).
It would basically a combination of existing technologies, but bundled in such a way that we can tell someone "just open this link" and your emails will magically be encrypted! Without having to explain about copying around PGP keys to each device and stuff. It's lower security, but arguably not lower than anything Aster/Tuta/Proton provide.
Or perhaps it would work better as an addon (so, a fork of Mailvelope)? That way people can continue using the interface they are used to, although since the email provider controls the interface they could be sending the email (eg. via autocomplete queries) before we even have time to encrypt it for sending.
We could apply a similar idea to an app as well: "install this app and use it to check your 'Gmail'".
If we follow some other innovative things like Google Inbox or Hey did/do it would help it catch on, but that would take more effort so maybe it's best to just put together existing stuff initially. If we use Horde, for example, then we can add those Inbox- or Hey-like features to Horde itself as plugins and let everyone benefit from it.
Life is TetrisMon 14 Sep 2026 7:11PM
What does the target audience uses e-mail for? Most people don't e-mail non-work contacts, and their work e-mails are not at threat at rest on their organization's storage.
Their e-mail is just a notifications system for financial events: shopping, banking, taxes. GMail reading all that is irrelevant to them when Google gets even more info off their phones.
Maybe the interesting audience is very small and is already using, say, Signal due to shortcomings of e-mail that encryption cannot fix.
Badri SunderarajanThu 17 Sep 2026 4:14AM
Documentation note: Thunderbird has a global end-to-end encryption setting and account-level end-to-end encryption settings. However, the global setting is only to "enable encryption when possible", i.e. if no keys are found it will silently fall back to sending an unencrypted message.
The account-level setting, on the other hand, is to "always enable encryption by default". If keys are not available, you will be forced to either try fetching keys or manually disable encryption. I think this option is better as we have to make a conscious choice about E2EE each time and it will also help with peer pressure.
Somewhat confusingly, the account-level setting is only visible if the global "enable encryption when possible" setting is disabled. If you enable the global option, then the account-level option doesn't show up.
So, if you are using Thunderbird, make sure to disable "encryption when possible" and instead go to the account settings so you can enable encryption even when it is impossible 😉
(If you have multiple identities per account and only some of those identities have PGP keys associated with them, you can find E2EE settings within each identity too, with the option to "always enable encryption" for that identity)
Badri SunderarajanThu 17 Sep 2026 4:40AM
What's the recommended way to handle shared email addresses (eg. for Prav's Treasury and Bursary teams)? Should we create a separate GPG key for the shared ID, or is there some way to indicate that "emails to this address should be encrypted for the following peoples' keys instead"?
Pirate PraveenThu 17 Sep 2026 8:18AM
We usually generate a key pair and share private keys with all members.
Buster KeatonFri 18 Sep 2026 5:56AM
I don't use it because the need never arises. And when it does arise, stop communicating with a friend is easier than getting them to convince the need for privacy.
Most of the communication happens over WhatsApp. And emails are for job applications, complaints, or for short communication with customer support. None of them have GPG keys.
Badri SunderarajanMon 21 Sep 2026 3:34AM
I have created a keypair for Prav's Bursary Team and am trying to get the same done for the Treasury Team. We could similarly set up a key pair for any public email addresses we have (eg. project contact)
Badri SunderarajanWed 30 Sep 2026 4:39PM
I was thinking we could have a better user interface for managing PGP webs of trust in a way that would appeal to non-technical users. This is related to email E2EE in the sense that it will make it easier to onboard people to PGP in general (if this becomes a big discussion we can move it to a separate thread).
Right now, the terminology is very geeky: we have keys with fingerprints and then we fetch them from keyservers and store it on our keyring using our agent. These are fine as metaphors for understanding how the underlying technology works, but not as metaphors for describe what it is that we want to do with the keys: identify people.
The software to manage keys is also very much centred around this technical metaphor. The most "user friendly" software I have used is Seahorse, because it has a GUI, and even that leans heavily into the keys metaphor.
My idea is: what if we instead designed a key management tool to be like an contact/address book?
To add someone as a contact, enter their ID (fingerprint), scan their QR code. Internally, we can use this to fetch the full key from a keyserver (in the case of QR codes, we could even design some more elaborate handshake involving signing).
To let people start adding you, you need to generate a persona (keypair) to start with. The reason I'm calling it "persona" is that people can create multiple personae, eg. for personal use or for a team.
At this point, we already have the peoples' names and email addresses, so the rest of the UI can present it in those terms with the fingerprint made smaller for reference and an option to add your own names etc. as with any other address book
Options to verify can remain unchanged—it means the same thing whether we are talking about keys or personae.
People communicate via channels other than email too. To be able to establish communication on other channels, we could allow the addition on arbitrary contact details in the form of a signed vcard. Here, we can add fields like XMPP, Date of Birth, (postal) Address, and ActivityPub (yes, I am aware that people don't usually communicate via Date of Birth, but they may want to do other things with it)
To retain privacy, a minimal vcard (or none) will be published by default, and you can decide to generate a vcard with other subsets of contact information to send to other people (eg. make one to share around at a conference). I am yet to think about an easy way for this distribution to happen
We could also publish vcards encrypted for specific personae if we only want those personae to be able to see those contact details. (This is similar to how Simplex Chat works for transmitting messages, although we should think a bit more about how we go about this as it could lead to storage issues).
[The most difficult part!] To use the persona on multiple devices or activate it on a new device, people need to remember to copy their persona file (private key) to the other device. This file should be kept locally and not put on any cloud storage service for example. For mobile applications, one way could be to transmit it in bits via QR codes similar to Thunderbird Mobile setup; another option is to make integrations for XMPP or email clients to do this more seamlessly (eg. by creating a temporary keypair to which to transmit the actual one when moving).
None of this is very groundbreaking in terms of technology, but it ties two standards (PGP and vcard) and presents them in the way that people are most often going to interact with these technologies. Even for me, it's less cognitive load to think that "I want to talk to @Ravi Dwivedi" rather than "I want to encrypt my email for for the GPG public key with fingerprint "FF7D B951 7CE1 E19B 6EFE 695F E0E5 BAFD 3BBF 70B3".
Ravi DwivediWed 7 Oct 2026 6:28AM
By the way, I have automatic encryption enabled in Thunderbird. If I don't have the OpenPGP keys of the person I am sending the email to, it attaches the OpenPGP keys along with the email without encrypting it. People outside the free software community usually get confused by this attachment.
Badri SunderarajanWed 7 Oct 2026 8:16AM
@Ravi Dwivedi these keys go out for me too but nobody has asked me about it yet. I was hoping they do so I can bring up E2EE but unfortunately they have not given me the opening 🥲
Badri Sunderarajan ·Sun 13 Sep 2026 4:58AM
As with other campaigns (eg. what we were discussing for DEPHCOM), I think it is best to provide recommendations depending on peoples' level of comfort and their existing setup.
People who are used to centralised webmail but are open to switching providers: switch to Aster or Proton (I would not recommend Tuta as there is no option to use other email clients even if people want to in future)
People who are stuck with their current proprietary webmail interface, such as Gmail, and do not want to switch: set up Mailvelope
Organisations who use Google Cloud for email on their own domain: switch to Aster, Proton, or Tuta if they allow organisation accounts (need to check this)
"Power users" who use mail clients (anything other than the default webmail offered by their provider): set up GPG encryption. If the client does not support GPG encryption, switch to Thunderbird on desktop (does it work on mobile?)
Power users who have GPG set up but are on a proprietary email service: switch to a privacy respecting email service such as Disroot or Riseup. If you are willing to pay, consider providers like Posteo, Soverin, Thundermail, and Mailbox.org (if you use your mail client often) or Aster and Proton (if you need SMTP access but use webmail often and are willing to set up a bridge for SMTP)
Organisations with power users: encourage your users to set up GPG encryption. If you are dependent on a proprietary service, switch to something privacy friendly such as Posteo or Mailbox.org
Power users who already have GPG set up: make sure your keys are available on a public keyserver (we should make a list)
Power users with published, active GPG keys: enable encryption by default on your email client
Power users with GPG who have a personal website: make the GPG keys available for download from your website
This is just a draft list, suggestions are welcome.