GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct key-gen example.

Browse Source
This commit is contained in:
Marcus Brinkmann 2011-05-12 14:42:18 +02:00
parent d11500a77e
commit f61abeb0cf
2 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/ChangeLog
View File

@ -1,3 +1,8 @@
2011-05-12 Marcus Brinkmann <marcus@g10code.com>
* gpgme.texi (Generating Keys): Fix OpenPGP parameters and reference
GPG and GPGSM manual.
2010-01-05 Werner Koch <wk@g10code.com>
* gpgme.texi (Changing Passphrases): New.

12
doc/gpgme.texi
View File

@ -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
<GnupgKeyParms format="internal">
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
</GnupgKeyParms>
@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
<GnupgKeyParms format="internal">