Version 1.0, 10.12.2013
deutsche Version (translation improvements are welcome)
The number of possible decisions is reduced as much as possible.
Showing the screen title on every screen (upper right) makes explanations and support easier.
Several key servers would be searched.
It should be possible to have additional user IDs displayed.
Screen: verify keys – info
It is insecure to import and use keys which you have not verified. You can verify them later but this can easily be forgotten. Not all applications show you a warning when you try to use non-verified keys.
For this reason this program imports new keys to a safe verification storage first. You can:
The verification storage is an additional keyring invisible to other applications.
Screen: import warning
key data:
Joe User <foo@example.org>
7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5
You are going to import a non-verified key. This is usually not a good idea.
It would make sense to not only import the key but certify it locally at certification level 1. In the configuration min-cert-level
would have to be set to 1.
Screen: verify key – info
key data:
Joe User <foo@example.org>
7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5
It is important that you have received this character string from the key owner in a secure way, on paper during face-to-face contact at best. Or by phone if that is not possible. In no case by email or from a web page or similar.
key is correct back to action selectionLocal signatures only. The Web of Trust is not for beginners.
Screen: key groups
action | short ID | user ID | |
---|---|---|---|
in verification storage only | |||
selection | 0x12345001 | Joe User <foo@example.org> | |
selection | 0x12345801 | Joe User <bar@example.org> | |
imported non-verified | |||
selection | 0x12345002 | Joe User <foo@example.com> | |
selection | 0x12345802 | Joe User <bar@example.com> | |
verified | |||
0x12345003 | Joe User <foo@example.net> | ||
0x12345803 | Joe User <bar@example.net> |
It should be considered whether to allow thr revocation of a verification.
On this screen it should be possible to have the program search the keyservers for all addresses in the local address book. It should be possible to have this repeated regularly so that the user can be informed about new crypto users among his contacts.
Screen: import key from file or clipboard
open file dialogpaste key text here:
Screen: my key for my contacts
show fingerprint print fingerprint sheets export key to file or key serverIf there are several secret keys then this screen needs a selection possibility.
Screen: my fingerprint
key data:
Joe User <foo@example.org>
7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5
It is important that your contacts receive this character string in a secure way, on paper during face-to-face contact at best. Or by phone if that is not possible. In no case by email or from a web page or similar.
On this screen there should be links to information about how to group user IDs.
Screen: send email to your contacts
Tell your contacts that you have started using crypto. We need every single user advertise it.
On this screen there should be a suitable text (maybe different variants for different groups) which e.g. points at this software. The user can copy this text to an email or have it opened in an email so that he just needs to select the recipients.
There should also be a link to information how everyone can support the usage of crypto, like http://userbase.kde.org/Concepts/OpenPGP_Help_Spread.