From f61abeb0cf9b820673cfecde6085cfc9e1a3ae58 Mon Sep 17 00:00:00 2001 From: Marcus Brinkmann Date: Thu, 12 May 2011 14:42:18 +0200 Subject: [PATCH] Correct key-gen example. --- doc/ChangeLog | 5 +++++ doc/gpgme.texi | 12 ++++++------ 2 files changed, 11 insertions(+), 6 deletions(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index d1ea943..638df32 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2011-05-12 Marcus Brinkmann + + * gpgme.texi (Generating Keys): Fix OpenPGP parameters and reference + GPG and GPGSM manual. + 2010-01-05 Werner Koch * gpgme.texi (Changing Passphrases): New. diff --git a/doc/gpgme.texi b/doc/gpgme.texi index c9bb708..c2bb309 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -3294,14 +3294,13 @@ used. GpgSM does not make the fingerprint available. The argument @var{parms} specifies parameters for the key in an XML string. The details about the format of @var{parms} are specific to the crypto engine used by @var{ctx}. Here is an example for GnuPG as -the crypto engine: +the crypto engine (all parameters of OpenPGP key generation are +documented in the GPG manual): @example -Key-Type: DSA -Key-Length: 1024 -Subkey-Type: ELG-E -Subkey-Length: 1024 +Key-Type: default +Subkey-Type: default Name-Real: Joe Tester Name-Comment: with stupid passphrase Name-Email: joe@@foo.bar @@ -3310,7 +3309,8 @@ Passphrase: abc @end example -Here is an example for GpgSM as the crypto engine: +Here is an example for GpgSM as the crypto engine (all parameters of +OpenPGP key generation are documented in the GPGSM manual): @example -- 2.26.2