Re:End-To-End – OpenPGP Chrome extension from Google
by tlrobinson on Tuesday June 03, 2014 @04:05PM
(#7842404)
Does this also mean parts of memory containing, say, passwords could be send to Google?
Re:End-To-End – OpenPGP Chrome extension from Google
by latj on Tuesday June 03, 2014 @04:51PM
(#7842648)
This "end to end" encryption happens in the browser. Google is the browser. Google dont need your keys, they have the plain text.
Re:End-To-End – OpenPGP Chrome extension from Google
by AJ007 on Tuesday June 03, 2014 @05:20PM
(#7842804)
Also, other browser extensions may be able to access what is going on in the browser. So Google and (insert list of other parties.)
Re:End-To-End – OpenPGP Chrome extension from Google
by woah on Tuesday June 03, 2014 @05:52PM
(#7842951)
Other software on your computer might as well. Or people walking by in the hallway. So Google and (insert everyone in the world).
Re:End-To-End – OpenPGP Chrome extension from Google
by opendais on Tuesday June 03, 2014 @04:56PM
(#7842682)
I think he was thinking the "Save Password" feature.
Re:End-To-End – OpenPGP Chrome extension from Google
by opendais on Tuesday June 03, 2014 @04:14PM
(#7842454)
I'd hope not. My guess is the extensions data in memory are included with the crash reports and it doesn't distinguish between extensions.
Re:End-To-End – OpenPGP Chrome extension from Google
by mixedbit on Tuesday June 03, 2014 @04:49PM
(#7842633)
Maybe encryption/decryption could be performed in a separate, isolated process, which stack would never be sent? It seems like Chrome multiprocess architecture could allow for this.
Re:End-To-End – OpenPGP Chrome extension from Google
by agarden on Tuesday June 03, 2014 @05:06PM
(#7842720)
Under "JavaScript crypto has very real risk of side-channel attacks": End-To-End’s crypto operations are performed in a different process from the web apps it interacts with.
Re:End-To-End – OpenPGP Chrome extension from Google
by mixedbit on Tuesday June 03, 2014 @05:16PM
(#7842781)
If process isolation is already done, disabling stack dumps for crypto processes seems like a logical next step that shouldn't be hard to accomplish.
Re:End-To-End – OpenPGP Chrome extension from Google
by magicalist on Tuesday June 03, 2014 @05:49PM
(#7842937)
It's probably relying on normal process isolation (and extensions run in a different process), but in order to disable stack dumps for it, you'd have to have some way of indicating "this process is special", which rules out treating it like any other extension.
Maybe there could be some new extension permission for "encryption extension" or something, but it's possible that could be abused...
Re:End-To-End – OpenPGP Chrome extension from Google
by tokenizerrr on Tuesday June 03, 2014 @06:00PM
(#7842989)
There's already permissions that are only usable by Google's own extensions, so they could do something like that.
Re:End-To-End – OpenPGP Chrome extension from Google
by opendais on Tuesday June 03, 2014 @04:56PM
(#7842679)
I'd agree that is better...but I am guessing that Google doesn't want to build this functionality directly into Chrome. Anyone who isn't Google wouldn't have the option for Chrome...Chromium isn't 'mainstream' :(
EDIT: Maybe the other guy is right and you didn't mean baking it into the browser. xD
Re:End-To-End – OpenPGP Chrome extension from Google
by spacefight on Tuesday June 03, 2014 @03:51PM
(#7842334)
That makes it largely unusable even to test for a few users, I guess.
Re:End-To-End – OpenPGP Chrome extension from Google
by danielweber on Tuesday June 03, 2014 @04:06PM
(#7842410)
If you are testing you are not mailing about nuclear secrets.
Re:End-To-End – OpenPGP Chrome extension from Google
by nobodysfool on Tuesday June 03, 2014 @03:53PM
(#7842347)
simple, just turn that feature off.
Re:End-To-End – OpenPGP Chrome extension from Google
by bildeman on Tuesday June 03, 2014 @03:56PM
(#7842363)
If you wanted this to be available for the general public then it could be slightly more troublesome.
I hope that has more than a FAQ warning when they release it to the Chrome Store. Otherwise....:/
It isn't perfect but it is probably the best in-browser option given the constraints available.