aboutsummaryrefslogtreecommitdiffstats
path: root/doc/DETAILS
diff options
context:
space:
mode:
Diffstat (limited to 'doc/DETAILS')
-rw-r--r--doc/DETAILS12
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/DETAILS b/doc/DETAILS
index a8acfe6ce..136447bfb 100644
--- a/doc/DETAILS
+++ b/doc/DETAILS
@@ -54,16 +54,22 @@ more arguments in future versions.
BADSIG <long keyid> <username>
The signature with the keyid has not been verified okay.
- ERRSIG <long keyid> <algorithm_number>
+ ERRSIG <long keyid> <pubkey_algo> <hash_algo> \
+ <sig_class> <timestamp> <rc>
It was not possible to check the signature. This may be
caused by a missing public key or an unsupported algorithm.
+ A RC of 4 indicates unknown algorithm, a 9 indicates a missing
+ public key. The other fields give more information about
+ this signature. sig_class is a 2 byte hex-value.
- VALIDSIG <fingerprint in hex>
+ VALIDSIG <fingerprint in hex> <sig_creation_date> <sig-timestamp>
The signature with the keyid is good. This is the same
as GOODSIG but has the fingerprint as the argument. Both
status lines ere emitted for a good signature.
+ sig-timestamp is the signature creation time in seconds after
+ the epoch.
- SIG_ID <radix64_string> <sig_creation_date>
+ SIG_ID <radix64_string> <sig_creation_date> <sig-timestamp>
This is emitted only for signatures of class 0 or 1 which
have been verified okay. The string is a signature id
and may be used in applications to detect replay attacks