It’s a simple ask, not bending over backwards. I bet they haven’t touched the email encryption part of code in years, so it doesn’t add any maintenance burden either. I’ve looked at what they do - the only thing they’d need to change is their handling of email headers!
Internally, yes. So, they only allow it if it’s under their control. This wouldn’t be a customer servie nightmare because only people who know how to use it would use it. Plus, their version of PGP doesn’t encrypt the subject.
No, you can set up PGP encryption to send PGP encrypted mail to non-proton customers via Proton. They’ve also been trying to work on standards that would make retrieving public keys/knowing the recipient accepts PGP automatic.
You’re blatantly misinformed, and it’s irritating.
Edit: I’ve blocked this person following their reply, but to their last point, “via Proton” literally means you use their service as a standard PGP mail client no strings attached, that can interact with any other PGP, and with no vendor lockin. That is literally the definition of using an open standard. There’s no insidious plot here.
Your tone and your assumption that everyone else is an idiot is irritating.
The key part of your first sentence is “via Proton”. Support for client side gpg is easy and they’re not doing it either out of some strategic play or purely out of stubbornness. Working on standarts is great! I’ve had a “Visionary” subscription to Proton for years, since before the VPN and all the extra stuff. I like the company, overall. But, as mentioned in my first comment, this is the singular most annoying part of their service to me.
It’s a simple ask, not bending over backwards. I bet they haven’t touched the email encryption part of code in years, so it doesn’t add any maintenance burden either. I’ve looked at what they do - the only thing they’d need to change is their handling of email headers!
https://github.com/ProtonMail/proton-bridge/issues/320#issuecomment-1350901372
Sounds more like an attempt to kill off gpg to win the market.
Jesus, they literally use GPG and integrate with 3rd party GPG. How did you make that leap?
Internally, yes. So, they only allow it if it’s under their control. This wouldn’t be a customer servie nightmare because only people who know how to use it would use it. Plus, their version of PGP doesn’t encrypt the subject.
No, you can set up PGP encryption to send PGP encrypted mail to non-proton customers via Proton. They’ve also been trying to work on standards that would make retrieving public keys/knowing the recipient accepts PGP automatic.
You’re blatantly misinformed, and it’s irritating.
Edit: I’ve blocked this person following their reply, but to their last point, “via Proton” literally means you use their service as a standard PGP mail client no strings attached, that can interact with any other PGP, and with no vendor lockin. That is literally the definition of using an open standard. There’s no insidious plot here.
Your tone and your assumption that everyone else is an idiot is irritating.
The key part of your first sentence is “via Proton”. Support for client side gpg is easy and they’re not doing it either out of some strategic play or purely out of stubbornness. Working on standarts is great! I’ve had a “Visionary” subscription to Proton for years, since before the VPN and all the extra stuff. I like the company, overall. But, as mentioned in my first comment, this is the singular most annoying part of their service to me.