name field restriction when creating key
Werner Koch
wk at gnupg.org
Mon Apr 24 14:58:54 CEST 2017
On Wed, 19 Apr 2017 18:01, dkg at fifthhorseman.net said:
> I also recommend that toolkit developers (like gpgtools) should use
> --quick-gen-key (assuming you're depending on the 2.1.x branch of GnuPG,
> which you should be in 2017), which accepts an arbitrary string as the
> full User ID (no distinction between different "fields" at all).
Let me add that GPGME wraps this into the new
gpgme_op_createkey
API. See:
https://gnupg.org/documentation/manuals/gpgme/Generating-Keys.html
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: </pipermail/attachments/20170424/de4b88a6/attachment.sig>
More information about the Gnupg-devel
mailing list