7 ms·
They've been working on a browser extension for it: https://googleonlinesecurity.blogspot.com/2014/06/making-end-to-end-encryption-easier-to.html https://googl
by schoen 11y ago
They've been working on a browser extension for it:
https://googleonlinesecurity.blogspot.com/2014/06/making-end-to-end-encryption-easier-to.html https://googleonlinesecurity.blogspot.com/2014/06/making-end...
https://github.com/google/end-to-end https://github.com/google/end-to-end
I don't know what they might do in the future to encourage people to use this, or if they feel that there's a point at which it would be sensible or useful to actively promote it.
- darkr 11y agoIt's still not ready for production use. One problem with e2e is that it's JavaScript based and runs in he browser, so there is a certain attack vector present there. To defend against this, ideally e2e needs to work with a smartcard (such as the yubikey neo) so that the private key cannot be stolen. There was an issue I was tracking a while back to integrate this support, but it's still a work in progress.
- viraptor 11y agoIt doesn't even need the hardware part in most cases. OS keyrings support pkcs11 interface with signing exposed. That means you can just send data to be encrypted for example by gnome-keyring and the browser never sees the actual key.
- darkr 11y agoBut e2e doesn't use the OS keyring. It uses it's own JavaScript keyring that runs in the browser and uses localstorage for storing private keys.