From a5fc1f40c36778dd24472b42bfd8b43e7c63f64f Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Tue, 17 Feb 2004 15:04:49 +0000 Subject: [PATCH] Added new options --- doc/gpgsm.texi | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/doc/gpgsm.texi b/doc/gpgsm.texi index 1c8b3071b..bf0e071b8 100644 --- a/doc/gpgsm.texi +++ b/doc/gpgsm.texi @@ -305,6 +305,16 @@ a line tagged @code{grp} is printed which tells you the keygrip of a key. This string is for example used as the file name of the secret key. +@item --with-validation +@opindex with-validation +When doing a key listing, do a full validation check for each key and +print the result. This is usually a slow operation because it +requires a CRL lookup and other operations. + +@item --with-md5-fingerprint +For standard key listings, also print the MD5 fingerprint of the +certificate. + @end table @node CMS Options @@ -730,7 +740,10 @@ To import certificates into the internal key database, the command @end example is used. The data is expected on the file descriptor set with the -@code{INPUT} command. Certain checks are performend on the certificate. +@code{INPUT} command. Certain checks are performend on the +certificate. Note that the code will also handle PKCS\#12 files and +import private keys; a helper program is used for that. + @node GPGSM DELETE @subsection Delete certificates