Key Mgmt GUI

[felix@hu.se (Felix Ungman)]

I'm designing a (public) key managament utility. I have no experiense with
cryptography, but I have worked much with GUI design. Please let me know
your opinion on the following questions.

1 - Is the key/keyring methaphor the easiest one to understand (both
respect to encryption and signatures)? Is there another better methaphor,
such as users (instead of keys) having a public and a secret id. For
example, Apple OCE uses the notation of signer objects instead of keys.

2 - Each keyring is naturally stored as a file. The obvious way to view a
keyring is to show a list of all keys in it. How much information should be
visible in the list, and how should it be presented (so that the user can
navigate thru very large keyrings)? Should the list include certificates?
If not, how are they managed.

3 - How should key pairs be treated? Should a user's public key be
"associated" with his secret key (and maybe stored together)? Should it be
possible to mix public and secrets keys in a keyring? Is it neccesary to
have a secret key ring when there's only one secret key?
----------------------------------------------------------------------
- RealName: Felix Ungman   InterNet: felix@hu.se   AppleLink: SW0358 -
-                     Felix gor det goda godare!                     -
----------------------------------------------------------------------