The point being made is that that means you must trust them with your private key, and you can’t have say two private keys - one for low security content they store, and one for more sensitive stuff where the key stays on hardware under your control.
You are literally trusting them to encrypt all your mail.
If you don’t trust their encryption, respectfully, don’t use them. It’s faux logic to “need” a secondary key that isn’t cloud synced in an end to end encrypted mail vault.
This is an unnecessary product complication, and I agree with proton that you’re more than likely to get it wrong and your “more secure” key will be used in a less secure manor.
It’s the same reason most people shouldn’t self host things like Bitwarden. Doing it yourself is not a security feature anymore than wiring your own home is protecting it.
This privacy community and the conspiracies or flat out misunderstandings that are coming back from the Reddit grave feel like they are coming from the anonymouse joker and Rob Braxman.
Why is that a fault in logic? The features are orthogonal. One doesn’t restrict the other. All other, normal, email providers allow client side gpg use.
You went to a custom shoe maker and said “make me a custom shoe” then you went back to them and said “I wanted to do it myself! Why won’t you let me change out the insoles in these shoes!”
That mentality is part of the problem. More options is not inherently better, it’s more to maintain, more complexity, more feature requests in that direction (“well can I store a PGP key in the browser that isn’t uploaded to your servers so I can read my non-synced PGP mail”, “can I write mail using that”, “oh I changed my mind, can I convert mail to your PGP key from my PGP key”, “oh I changed my mind again, I’d actually like all my emails changed to my PGP key”, “oh could you sync my PGP key for me”, etc).
It happens all the time, bending over backwards as a company for niche customers that want to use your toaster as a waffle iron rarely works out well.
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!
That’s not true at all, you just upload your key into the encrypted account storage, and it gets automatically applied.
I don’t want to upload anything. Why would they ever not allow that?
The point being made is that that means you must trust them with your private key, and you can’t have say two private keys - one for low security content they store, and one for more sensitive stuff where the key stays on hardware under your control.
You are literally trusting them to encrypt all your mail.
If you don’t trust their encryption, respectfully, don’t use them. It’s faux logic to “need” a secondary key that isn’t cloud synced in an end to end encrypted mail vault.
This is an unnecessary product complication, and I agree with proton that you’re more than likely to get it wrong and your “more secure” key will be used in a less secure manor.
It’s the same reason most people shouldn’t self host things like Bitwarden. Doing it yourself is not a security feature anymore than wiring your own home is protecting it.
This privacy community and the conspiracies or flat out misunderstandings that are coming back from the Reddit grave feel like they are coming from the anonymouse joker and Rob Braxman.
Why is that a fault in logic? The features are orthogonal. One doesn’t restrict the other. All other, normal, email providers allow client side gpg use.
What is the benefit to using your own key on top of protons encryption? Why not just use your own encryption with any other provider?
One less email to have? Wdym???
Put another way…
You went to a custom shoe maker and said “make me a custom shoe” then you went back to them and said “I wanted to do it myself! Why won’t you let me change out the insoles in these shoes!”
Yes, what’s the problem with that? Services should provide as much flexibility as possible.
That mentality is part of the problem. More options is not inherently better, it’s more to maintain, more complexity, more feature requests in that direction (“well can I store a PGP key in the browser that isn’t uploaded to your servers so I can read my non-synced PGP mail”, “can I write mail using that”, “oh I changed my mind, can I convert mail to your PGP key from my PGP key”, “oh I changed my mind again, I’d actually like all my emails changed to my PGP key”, “oh could you sync my PGP key for me”, etc).
It happens all the time, bending over backwards as a company for niche customers that want to use your toaster as a waffle iron rarely works out well.
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