Allow to generate own keys and only upload pub key
breznak opened this issue · comments
So the private key is totally kept local. Only accessed when reading messages.
Private key is never uploaded to Google.
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.