Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to generate own keys and only upload pub key #41

Open
breznak opened this issue Feb 28, 2017 · 2 comments
Open

Allow to generate own keys and only upload pub key #41

breznak opened this issue Feb 28, 2017 · 2 comments

Comments

@breznak
Copy link

breznak commented Feb 28, 2017

So the private key is totally kept local. Only accessed when reading messages.

@sirdarckcat
Copy link

Private key is never uploaded to Google.

@eduncan911
Copy link

eduncan911 commented Jul 3, 2017

But some of us already have our own PrivateKeys for email addresses dating back many many years, published and readily available in the WOT.

Users that are not "e2email" users, would get confused as to which PublicKey to use: the one the owner, us, published or the one that e2email published in its own keyring.


Maybe we are mis-understanding. Does e2email create standard PGP-encrypted-n-signed emails that non-e2email clients are supposed to be able to decode?

If so, this issue is valid. We already have our own public and private keys we use.

If not, then e2email is strictly for "in the know" users that must use Chrome and must use e2email extension - which severely would limit its adoption rate I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants