Page MenuHome GnuPG

more precise wording in option lists
Closed, ResolvedPublic

Description

I think the option lists could be worded more precisely, whilst retaining its
current simplicity. Currently, we have:

++ (1) RSA and RSA (default)
++ (2) DSA and Elgamal
MS (3) DSA (sign only)
MS (4) RSA (sign only)
S (5) Elgamal (encrypt only)
S (6) RSA (encrypt only)
MS (7) DSA (set your own capabilities)
MS (8) RSA (set your own capabilities)
++ (9) ECC and ECC
MS (10) ECC (sign only)
MS (11) ECC (set your own capabilities)
S (12) ECC (encrypt only)
S (13) Existing key

This is confusing in a few ways:

  1. "sign only" actually means "sign and certify"
  2. "X and Y" actually means "X master and Y subkey"
  3. "set your own capabilities" includes encryption only in the case of RSA

I am happy to keep using "sign" to mean "sign and certify", since certify is a
cryptographic signing operation; but the others could be clearer. So instead, I
propose:

++ (1) RSA (sign) and RSA (encrypt) subkey (default)
++ (2) DSA (sign) and Elgamal (encrypt) subkey
MS (3) DSA (sign)
MS (4) RSA (sign)
S (5) Elgamal (encrypt)
S (6) RSA (encrypt)
MS (7) DSA (custom capabilities, except encrypt)
MS (8) RSA (custom capabilities)
++ (9) ECC (sign) and ECC (encrypt) subkey
MS (10) ECC (sign)
MS (11) ECC (custom capabilities, except encrypt)
S (12) ECC (encrypt)
S (13) Existing key

You could also leave out "subkey", if you feel that is too verbose.

Details

Version
2.1.0

Event Timeline

infinity0 added projects: Feature Request, gnupg.
infinity0 added a subscriber: infinity0.

(My suggested examples also have some visual similarity between actually similar
options.)

werner claimed this task.
werner added a project: Won't Fix.

Nope. We discussed this already at the ML.

You responded to my previous suggestions, and this is my next iteration, with me
trying to take into account your comments.

I find that making related options visually related, helps the user to better
intuitively understand what they do. The current options don't do this.

You also had a comment along the lines of "sign is not accurate because there's
also certify and authenticate", but a few current options also have this flaw. I
think it's OK, but it's better to do this consistently.