|
Top-level
 @fidel Yes, I briefly read about it, but it doesn't make much sense, I have my own gpg key and can encrypt it whenever I need and want. Also, I had a conversation with a proton mail user and I recieved email from them encrypted, however I couldn't reply back with encryption, because it seems proton doesn't expose pgp public key via WKD (it could be related to additional setup not done on custom domain). 6 comments
 This is why I send the public key as a attachment in every mail. This way you just import it. On https://account.proton.me/u/0/mail/encryption-keys you can also import keys for advanced users like you. Proton mail doesn't want to be able to read your mails so your browser needs to unlock your mailbox. IMAP would require them to be able to read your mailbox so they provide you with the bridge so you can install IMAP on a host YOU trust. @dgr @fidel I understand why the proton bridge is needed for imap access to proton, but I don't think it's right architectural decision. migadu's approach looks more apropriate to me: @abcdw @fidel Not quite understand there approach from the link. @dgr @fidel The approach is to stick to vanilla emails without forced encryption and custom gui apps to access your emails via standard protocols. If you want encryption, encrypt it with your usual pgp tool. Personally, I don't see how proton and similiar services improve something, but I clearly see how they make it harder to use standard tools. |
Gregory's Server
@abcdw Not that you want to, but Protonmail supports using your own PGP private keys: https://proton.me/support/importing-openpgp-private-key
Protonmail aims to make encrypted email easy, but that means that you are probably not their target audience.