search

google / end-to-end

End-To-End is a crypto library to encrypt, decrypt, digital sign, and verify signed messages (implementing OpenPGP)
Apache License 2.0
4.13k stars 298 forks source link

Imported public key name doesn't contain valid email address. #132

Closed koto closed 9 years ago

koto commented 9 years ago

From godisgovernment on June 29, 2014 22:41:58

Steps to reproduce:

  1. Import third party's public key (I imported from gmail message).
  2. Notice that key name seems to be forced to "-"
  3. When inserting message into gmail's compose box, the email will be set to the name of the key being used, which is an invalid address.

What happens?
The "To:" address is invalid and has to be manually adjusted in the compose window.

What do you expect to happen instead?
I would expect the name of the key stored into the keyring to be formatted properly, manually editable, or stored in some way that end-to-end will relate the key to a proper address to insert into the compose window.

Original issue: http://code.google.com/p/end-to-end/issues/detail?id=95

koto commented 9 years ago

From koto@google.com on June 30, 2014 10:49:36

Status: Started
Owner: koto@google.com

koto commented 9 years ago

From koto@google.com on June 30, 2014 10:56:55

Public key User IDs should contain e-mail addresses ( http://tools.ietf.org/html/rfc4880#section-5.11 ) If that's missing, there's little we can do. Editing the user id is discouraged against. That being said, I fixed the error that would put the invalid e-mail address into Gmail compose window.

Status: WontFix

koto commented 9 years ago

From evn@google.com on July 21, 2014 16:30:05

Labels: Component-Logic Usability