6 ms·
From the Stanford JS Crypto library's page: > (Unfortunately, this is not as great as in desktop applications because it is not feasible to completely protect
by IgorPartola 13y ago
From the Stanford JS Crypto library's page:
> (Unfortunately, this is not as great as in desktop applications because it is not feasible to completely protect against code injection, malicious servers and side-channel attacks.)
The browser is not a secure environment and cannot be. You cannot guarantee security in the browser even if you control the server-side of the application, let alone when someone else does. In other words, Google can still read every bit of email you send/receive in cleartext.
The only way I see how one could make something like this work is by creating a browser plugin where the cleartext runs outside the context of the browser process (perhaps in Java?). If cleartext ever exists inside a JavaScript interface, it's game over.
I upvoted this post because we do need more discussion of security and especially usability of security. However, unfortunately, this provides no real security.
- benregenspan 13y agoWhile the security granted by this may be imperfect, "no real security" seems like a bit of a stretch. This eliminates the main pathways by which governments obtain access to email (subpoena of the service provider and straightforward interception of the mail as it is transmitted). Combine that with a webmail service like Gmail where the company providing it has a very real incentive to prevent code injection, and with browser vendors being exceptionally fast at finding and patching exploits, and it's hard to say that this isn't far better than nothing at all.
- IgorPartola 13y agoGMail has a very real incentive to read all your mail. As soon as this plugin gets any real traction Google will trivially circumvent it.
- grimtrigger 13y agoSeems unnecessarily pessimistic. AdBlock has been on the chrome store without much issue despite being directly opposed to Google's business model.
- IgorPartola 13y agoThe US government creating a secret law that authorizes a secret court to order Google to siphon all of its cleartext data to the NSA is also a bit pessimistic. The value proposition of the featured plugin is that it protects you from Google snooping on what you do through the means of technology. While I am very glad there is a discussion of the subject, I am saying that the technology the plugin uses is fundamentally flawed and can never be fixed. Because of that, it provides no real security. It is in the same league as setting the root password on your server to "root" and changing the sshd port: obscure but not secure.
- ams6110 13y agoYeah really the way to provide security in gmail is to compose your message in an external (local) editor, GPG and ascii-armor the message, paste that into gmail, and send it. The recipient does the reverse. Using an editor like emacs could make this pretty streamlined, but at that point you might as well just use an IMAP client that can do GPG or S/MIME.