Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Help users deal with UIDs with multiple keys #76

Open
koto opened this issue Dec 16, 2014 · 6 comments
Open

Help users deal with UIDs with multiple keys #76

koto opened this issue Dec 16, 2014 · 6 comments

Comments

@koto
Copy link
Member

koto commented Dec 16, 2014

From [email protected] on June 07, 2014 02:28:11

When you have multiple private keys for a single email address, there is no way to select which key is used.

Reproduction steps:

  1. Import multiple private/public keys for a single email address
  2. Attempt to sign/encrypt a message, selecting this email address as the from field.

What do you see?
The message is signed/encrypted. The first private key listed on the options page is used.

What do you expect instead?
To be able to select which key does the signing. It would also be great to be able to set the default key after importing them.

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

@koto
Copy link
Member Author

koto commented Dec 16, 2014

From [email protected] on June 06, 2014 19:16:33

Labels: Type-Enhancement Priority-Medium Component-UI Usability

@koto
Copy link
Member Author

koto commented Dec 16, 2014

From [email protected] on June 16, 2014 04:01:36

hey radi, wdyt we should do here

Owner: [email protected]

@koto
Copy link
Member Author

koto commented Dec 16, 2014

From [email protected] on August 11, 2014 21:37:23

Ping o.o

@koto
Copy link
Member Author

koto commented Dec 16, 2014

From [email protected] on August 12, 2014 00:51:40

Sorry for the delayed response. I'm doing some refactoring in the prompt UI. This can certainly be solved in the process.

@sirdarckcat
Copy link
Member

cleaning up old bugs, please reopen if you would still like to see this fixed

@tildelowengrimm
Copy link

This seems like something which should definitely still be fixed. If you have multiple keys for an email address, you should be able to pick the right one — or at least somehow resolve that conflict with a user decision.

@koto koto reopened this May 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants