4 ms·

I have no idea how to get that extension or how to install it. Is there some simple guide? edit: all I see here https://github.com/google/end-to-end https://

by runn1ng 12y ago

I have no idea how to get that extension or how to install it. Is there some simple guide? edit: all I see here https://github.com/google/end-to-end https://github.com/google/end-to-end is We’re releasing this code to enable community review; it is not yet ready for general use

nacs 12y ago
They have a Wiki that has build/install instructions: https://github.com/google/end-to-end/wiki/Build-instructions https://github.com/google/end-to-end/wiki/Build-instructions. Basically, clone the Git repo then do: ./do.sh install_deps ./do.sh build_extension This results in an extension folder that can be installed via Chrome's developer mode. Disclaimer: not affiliated in any way and never used it myself
- Fastidious 12y ago
  That is the way I built it. I wanted to add that java is required.
tim333 12y ago
Interesting that they've had a vulnerability reward program since June 2014. I wonder how that's getting on http://googleonlinesecurity.blogspot.com/2014/06/making-end-to-end-encryption-easier-to.html http://googleonlinesecurity.blogspot.com/2014/06/making-end-...
- sondh 12y ago
  They provided an update last December[1] and stated that two rewards have been given. The same update is also interesting because it mentioned the migration from Google Code to Github (three months ago!). The blog post talked about Yahoo! contribution to the project too... [1] http://googleonlinesecurity.blogspot.com/2014/12/an-update-to-end-to-end.html http://googleonlinesecurity.blogspot.com/2014/12/an-update-t...
alkonaut 12y ago
A Windows build environment is not supported. Wonder what they thougt there? Windows is where the majority of users are, it's where the people who can't (or don't want to) use command line tools for encryption are. Why would you even approach this from a Linux-first angle? I'd understand if it was because the developers are typically Linux users and they want it thuroughly tested before shipping a user friendly version (i.e chrome ext for windows).
- sarciszewski 12y ago
  It's not ready for consumers yet. The end result will be a Chrome extension anyway.

by runn1ng 12y ago

nacs 12y ago

They have a Wiki that has build/install instructions: https://github.com/google/end-to-end/wiki/Build-instructions https://github.com/google/end-to-end/wiki/Build-instructions. Basically, clone the Git repo then do: ./do.sh install_deps ./do.sh build_extension This results in an extension folder that can be installed via Chrome's developer mode. Disclaimer: not affiliated in any way and never used it myself

Fastidious 12y ago
That is the way I built it. I wanted to add that java is required.

tim333 12y ago

Interesting that they've had a vulnerability reward program since June 2014. I wonder how that's getting on http://googleonlinesecurity.blogspot.com/2014/06/making-end-to-end-encryption-easier-to.html http://googleonlinesecurity.blogspot.com/2014/06/making-end-...

sondh 12y ago
They provided an update last December[1] and stated that two rewards have been given. The same update is also interesting because it mentioned the migration from Google Code to Github (three months ago!). The blog post talked about Yahoo! contribution to the project too... [1] http://googleonlinesecurity.blogspot.com/2014/12/an-update-to-end-to-end.html http://googleonlinesecurity.blogspot.com/2014/12/an-update-t...

alkonaut 12y ago

A Windows build environment is not supported. Wonder what they thougt there? Windows is where the majority of users are, it's where the people who can't (or don't want to) use command line tools for encryption are. Why would you even approach this from a Linux-first angle? I'd understand if it was because the developers are typically Linux users and they want it thuroughly tested before shipping a user friendly version (i.e chrome ext for windows).

sarciszewski 12y ago
It's not ready for consumers yet. The end result will be a Chrome extension anyway.