4 ms·
Correct me if I'm wrong, but you're encrypting the message after you type in into the webmail client but before you send it? We all know that GMail constantly
by chrissnell 12y ago
Correct me if I'm wrong, but you're encrypting the message after you type in into the webmail client but before you send it? We all know that GMail constantly saves auto-drafts to server-side as you type. If your GMail is being monitored by a government (and we should assume that it is), this type of encryption client isn't going to do much for you. You'd be better off typing it in a text editor and encrypting that and pasting in.
- greenpizza13 12y agoSeems like this opens a new window, separate from gmail, to type the message into. This window would not be sending the copy to gmail to save as draft, etc.
- galapago 12y agoYou type your message in a special window/box, controlled by the plugin so the webmail can't read it. In fact, Mailvelope was audited to check that malicious javascript in the server can't read your plaintext.
- mncolinlee 12y agoNever mind all the other obvious problems that could occur at any stage. The webmail server could change a single setting and record every keystroke. An intelligence agency could push an updated version of the extension which records keystrokes or quietly caches plaintext. A browser update could detect the extension and start recording everything. Any time you try to make encryption simple and easy for a mass audience you still have to educate the user about risks. Most solutions are not bulletproof enough to keep out intelligence agencies.
- oh_sigh 12y agoWith a chrome plugin, a window can be created with the running page does not have access to. I'm pretty sure that is what this plugin is using