railcas.blogg.se

This problem? I’d be interested in reading any comments that you have That you serve? If so, has ProtonMail considered any solutions to ProtonMail to access users’ secrets by modifying the client-side code Specifically, if ProtonMail were to go rogue, would it be possible for I’m curious if ProtonMail has any comment on this subject. What’s wrong with in-browser cryptography in 2017? Solution to the ‘Browser Crypto Chicken-and-Egg Problem’? Some interesting ideas around solutions to this problem:Ĭan protonmail access my passwords and hence my secrets? Some of these questions (and their ensuing responses) also contain where this subject has come up recently. Server with your secrets, than how can users trust the server to serveĬopied below are links to a few questions on ‘The Browser Crypto Chicken-and-Egg Problem’ by security researcher Keys or plaintext information, and sends these secrets back to the Protonmail’s servers, such that the code captures the user’s private Were to ‘go rogue’ (or if ProtonMail were to be coerced, or if anĪttacker were to gain access to ProtonMail’s servers, etc.), it wouldīe possible for ProtonMail to modify the client-side code served by However, it would seem that if ProtonMail ‘your data is encrypted in a way that makes it inaccessible to us’,Īnd ‘data is encrypted on the client side using an encryption key that On in-browser crypto to implement ‘zero-access’ systems), in theĬontext of the ‘Browser Crypto Chicken-and-Egg Problem’. Have come up recently about ProtonMail (and other services that rely I am a moderator at, and several questions Managed to make end-to-end encrypted email as simple to use as I've not received a response from Protonmail as of yet, but if/when I do, I will update here.įirst off, I’d like to thank you for building ProtonMail. I sent the following email to on, inviting Protonmail to weigh-in on this subject. If you can't trust the server with your secrets, then how can you trust the server to deliver secure code? See for some good reading on this subject. This is why javascript cryptography is a 'chicken-and-egg' problem. Then, they would have everything necessary to decrypt your private key, and then decrypt your messages.

If protonmail were to be compromised, or if protonmail were to 'go rogue', they could easily serve javascript that captures your password after you enter it, and sends the password back to their servers. However, the SRP is implemented in javascript, which is served by protonmail's server.

Therefore (under normal circumstances) your password is never sent to protonmail's server. Xavier59's answer is correct, in that protonmail uses SRP.