This private key cannot be exported from the key itself. Some of us use yubikeys and nitrokeys with the private key stored on such a hardware token. When also sending works fine with external keys, the Bridge gives a pretty good starting point for "normal use cases", delivering a secure base service with possibility for even higher security for the advanced use cases - all this without adding even more complexity than strictly needed.Īnd if you wonder why external keys are needed. The Bridge is also getting into shape (still a few things missing, though) to better handle both encrypted and signed mails using external keys (not known by ProtonMail). The Bridge solves that issue nicely and mostly isn't ending up as an obstacle to the users. Which would degrade the security of the service to a plain unencrypted email service. This complexity is most likely too much for even many of those capable of doing it. Plus getting each recipients public key added to really enable E2EE. Here is the code which I tried to run and failed me: import smtplib server smtplib.SMTP ('127.0.0.1', portnumber) server. But it would require the mail client to be set up correctly with PGP support and the private PGP key from ProtonMail to work. Add your domain name to the domain page in your email provider account if you havent done this. Well, it could theoretically be possible to provide the PGP encrypted data via such an IMAP connection. To connect an external email: Go to your email settings page.
0 kommentar(er)
