[PATCH libgcrypt] * gcrypt.h.in: Set appropriate algo id for ECDSA and ECDH

Kristian Fiskerstrand kristian.fiskerstrand at sumptuouscapital.com
Mon Nov 19 09:40:39 CET 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11/19/2012 08:35 AM, Werner Koch wrote:
> On Sun, 18 Nov 2012 19:08, kf at sumptuouscapital.com said:
> 
>> Currently a request for e.g. gcry_pk_algo_name with argument 18
>> or 19 will return "?" rather than the appropriate name for the
> 
> 18 and 19 are not assigned.  Thus a question mark is returned.
> 

Thanks for the clarification. I was under the impression that this
happened with RFC6637, but I reckon that this has not been formally
accepted yet and still remain in a proposed status.

FWIW, the "?" is then passed along to GnuPG and is used for e.g
gpg2 --search kf at sumptuouscapital.com (key 0x542CA00B) , when querying
subset.pool.sks-keyservers.net (which require keyservers to be
upgraded to SKS 1.1.4 or higher, that has the draft version of RFC6637
implemented). I just noticed this while playing around with adding
SSL/TLS to the dirmngr for hkps support.

- -- 
- ----------------------------
Kristian Fiskerstrand
http://www.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
"I never worry about action, but only inaction."
(Winston Churchill)
- ----------------------------
This email was digitally signed using the OpenPGP
standard. If you want to read more about this
The book: Sending Emails - The Safe Way: An
introduction to OpenPGP security is
available in both Amazon Kindle and Paperback
format at
http://www.amazon.com/dp/B006RSG1S4/
- ----------------------------
Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.0-beta95 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBCAAGBQJQqfCDAAoJEAt/i2Dj7frjoEAP/jx9IT+2ZrwX+zXRt9OUu/O2
IFEtcnxq5y+2cqnQZecz/iUx5NXp9M9pbU+GrYFCjeWKux8bj3OAQ6g7lIINX5yC
yFLwNyG3L/JG7Bh48jLkOWg/SWKIxaeN8Zi2iwY8FM6EkRXUGX921+LeWZg/D5/S
u/i1QK89IwLOrNBbliJ/dPZoIqELvN89CpyjbDOYJmFoA0qWgT6/0p1DazByiTsw
A7U2yGnx0/o+EFRA5toV9KKmaozj9wj7AGLSIrBlWdE3DVRiIdAU00QyAm8MyBX3
4SCdlCEgfDuASGmE7q7YyBt+btCX8hOn01a31PuTzLTSSpSxCt2shZe+BbxGbhbg
pk+5b/aXjjWbn76L7Vsdy5LdcDKmrnqBQA771CdvF9sb870XV9sjiKm47Te1x5KG
O5wbAH2UmtOBKworrf0jKd7wBvWuRzX5iGdsAImgVHWlmoGVyq+yHmx2DfiVcUiV
WwEbCm1XZmWBsgV5cTLHVoNdBGIisOozXNjLPVyDqOZX2MWi0IAStgTaZWMBvx+9
o7yRdXd+yzf/sGgnVTRhTScPajIFjYkqsx0sGiEN6vjzPXe+SB72p4g3uyPwWmyv
8ehM7BTu+eJoiT3eRb726QeijfnSE+fcKWYWibts9+7FK5KDBC6wg/GrpkXr/rJs
/Mot4l9hnVOIB8cwHmLS
=7L7G
-----END PGP SIGNATURE-----



More information about the Gnupg-devel mailing list