search

ag-mailcrypto / storm-plugin

Thunderbird plugin to implement the STORM encryption concept, not based on enigmail
GNU General Public License v3.0
6 stars 0 forks source link

List of secret keys #10

Closed gnomus closed 11 years ago

gnomus commented 11 years ago

Create the "My Keys" List and remove own keys from "Other's Keys"

Fix trust icons in secret key list.

opatut commented 11 years ago

Well the secret keys are in the "My Keys" list, but your own public keys are in the public key ("Other's Keys") list, too (since they are actually public keys). How should we handle this? Remove them from Other's Keys and move own-public-key-management to "My Keys"? Discuss!

malexmave commented 11 years ago

Is this a frontend or backend decision? I think that in the backend, it would be best to have your own pubkey in the list of "Other's keys" as well, since you only have to check one list for matching keys when sending a mail (else you would have to search both "Other's" and "My" Keys for matching pubkeys or you would be unable to send yourself encrypted messages).

In the frontend: I am not sure what arguments could be made in favour of either idea. I think both of them have their merits, and we should get the opinion of a UX person on this.

opatut commented 11 years ago

This is all about frontend. In backend, of course, we have the list of public keys, which includes your own.

malexmave commented 11 years ago

UX = User Experience. So, in our case, a MCI student, or possibly our contact in bremen.

opatut commented 11 years ago

After discussing with @mquintus we decided it might be useful to just show the matching pubkey's status in the list, so expired/revoked keys would show up red. Yellow should be no issue then (since you usually trust your public key when you self-sign it, right).

opatut commented 11 years ago

Closing since this sub-issue was reopened as #24.