Google Announces 'End-To-End' Encryption Extension For Chrome
Nexus Unplugged (2495076) writes 'On their security blog today, Google announced a new Chrome extension called "End-To-End" intended to make browser-based encryption of messages easier for users. The extension, which was rumored to be "underway" a couple months ago, is currently in an "alpha" version and is not yet available pre-packaged or in the Chrome Web Store. It utilizes a Javascript implementation of OpenPGP, meaning that your private keys are never sent to Google. However, if you'd like to use the extension on multiple machines, its keyring is saved in localStorage, which can be encrypted with a passphrase before being synced. The extension still qualifies for Google's Vulnerability Reward Program, and joins a host of PGP-related extensions already available for Chrome.'
Google also published a report showing how much email is encrypted in transit between Gmail addresses and those from other providers.
From joe scriptkiddy sure, but not from the people you actually don't want reading your mail.
1: Compatible with OpenPGP (except for some reasonable caveats. Not bad.)
2: Some thought in building it, not just slinging a beta for download, wise.
3: Keys stored away from where the bad code can compromise a browser... smart.
So far, this seems to be something that can be useful for one who does use PGP or gpg often.
End-To-End doesn’t trust any website's DOM or context with unencrypted data.
I think this is the most important sentence in TFA, as it shows this is a real user-side-DRM (enforcing pivacy rights) in browsers.
Seeings as the FBI fought Phil Zimmermenn a former political activist and the writter of PGP tooth and nail in court over it I would guess that they don't have a backdoor.
---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
How would that help?
What would me, you, or him reading the code accomplish? I guaranty that none of us would spot an NSA level backdoor.
Open Source guarantees optimal security, if you are one of the top ten security professions on the planet and basically have enough time to write the software yourself.
Troll is not a replacement for I disagree.
At first glance, this looks like a good idea which should be encouraged and nurtured. Even if they fuck up something.
The downside is that it's pretty crazy to be doing stuff like this in a scripting language inside of a machine that downloads new versions from somewhere, at the drop of a hat, and where the machine itself (Chrome) is remotely-coercible. (In other words, point a gun at Google's head, and they will extract your key the next time you enter your passphrase.) But really I think this is a minor point! (bear with me; I know that sounds like a bombshell.)
It's good to for people to start using OpenPGP, even if they do some things wrong, and for it to get more mainstreamed. It'll get 'em familiar with the concepts (and they need to learn them all; take anything out and you have a broken system), and then some day they will graduate to the real thing (actual PGP or GnuPG, outside the vulnerable context of today's web browsers) and do things more carefully on their own time while remaining interoperable with their associates.
I know I am a dead-horse beater on this, but OpenPGP, after all these years, really is still the very best, top-notch, number one PK system we have. It's not merely good; it's right. And the applications for the WoT go far beyond merely securing communications from snooping, though it happens to be excellent that that. Three cheers for Google not inventing something gratuitously nonstandard (and therefore, probably deficient)!
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.