These should all be easy to fix, so to cut down on your overhead of closing
issues, I decided to put these all in one place. If you prefer otherwise, just
let me know.
- The fact that revocation certificates are generated, is mentioned no-where.
They should be mentioned at least:
- in the man page for --gen-key
- after the key generation process is finished
The wording in the revocation certificate itself is quite good, however "use it"
would not be clear to novice users. Instead, I would start off something like:
This is a revocation certificate for your key. Think of it as a "kill switch".
To use it, import it (--import) into your keyring and then publish the public
key (--send-key) to keyservers.
[..]
As with normal kill switches, this revocation certificate may be abused; if you
feel more comfortable without it, then you may delete this file. Note that you
cannot generate a new one without the secret key, and knowing its passphrase.
- Double redirect about batch mode using ambiguous wording.
In the man page for gpg, it says:
--gen-key
[..] There is also a feature which allows you to create keys in batch mode.
See the file ‘doc/DETAILS’ in the source distribution on how to use this.
In DETAILS, it now (since 2.1.0) says:
- Unattended key generation Please see the GnuPG manual for a description.
"X manual" is a generic term and it's not clear that this refers to a specific
document; "GnuPG manual" is not mentioned anywhere else in DETAILS. It would be
better to remove this section from DETAILS. In the man page for --gen-key, one
can point to the SEE ALSO section, which defines what the manual is and mentions
that info gnupg is available for offline users.