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

Kristian Fiskerstrand kristian.fiskerstrand at sumptuouscapital.com
Tue Nov 27 20:46:51 CET 2012


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

On 11/27/2012 08:21 PM, Werner Koch wrote:
> On Tue, 27 Nov 2012 18:07,
> kristian.fiskerstrand at sumptuouscapital.com said:
> 

...

> 
>> server name. This cause issues with keyservers on e.g. virtual
>> host settings that are expecting the specific name or the pool
>> names to be
> 
> A virtual HTTP host for a keyserver?  I doubt that this is a good
> idea. Thanks for this heads up.

This is typically related to putting SKS behind a reverse proxy due to
[0] or to enable HKPS[1] since it defaults to 443 (hence also the SNI
requirement). Personally I'd prefer a non-standard port for this (as
we have for HKP), but too late for that, so have to rely on SRV
records as an alternative, although that is made more difficult due to
issue1446 [2]

[0] http://lists.gnu.org/archive/html/sks-devel/2012-03/msg00006.html
[1] http://lists.gnu.org/archive/html/sks-devel/2012-10/msg00000.html
[2] https://bugs.g10code.com/gnupg/issue1446



- -- 
- ----------------------------
Kristian Fiskerstrand
http://www.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Quidquid latine dictum sit, altum videtur.
Anything said in Latin sounds profound
- ----------------------------
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-beta100 (GNU/Linux)

iQIcBAEBCAAGBQJQtRiqAAoJEAt/i2Dj7frjprsQAJVRtOJMcF6uVq+/70MVTs9Y
owzzAXnyBZjWn6mh28MMLK4Vl99kLawJif1jpmAZIKepCjBTs/spuK7z+kzJHLLn
J2mfF57ZI0ck8c65w56vbtDx6i0l3/ubMSooi8K5IRzfbqAFVQtFSn/jDgES/d7J
OZnSti8madykwSqpOTfOVVMQiWbG5mBQtrG7IzE66M2FbsJFSxXQMz7v5sgp1q3X
MMArRlPh6DhY/3KBF+g8KbDmOAj3AJ1m5Ht+gkFsPF4lwDVOnRHCAhHizi/Q7oUd
sTqOPD4SecOcJJkkkqbPy08Atc0nuctP8Y15BRbpC3zDoc3uypD4CAnvCRHNsupu
ABkTpLvaaXDI1OLxy2LIf97te5v6nI6IOL7Sql4qxyN/+qpcRQZeHVDlZNP2m3d0
+35XfbBJ+ZeKPdPejuBJHbb3AEMNeGCE/POLC4/HJ2WebO3qMabXq3TcsUMDF3Na
orFjHjK5hgUZwAkZGw+pp0M9YMPDzfUqYAnEx+D2XeW9F1ymQGmriVP5duXtcJUf
iFmR3OcqhSjdEVxjotdIzk+ApYqMmTSZ2iJeEHddPA6oJiAjCBg2n2QGjAbM4pMQ
y4zYyr4DAjyl7ZVWLgGAFxUKZ96wFjhX65+ZC6q5DTEgdDIt7Vj3HXzHBv9AZLbl
nIgYqJIjcJdeyODhWsjG
=tfcB
-----END PGP SIGNATURE-----



More information about the Gnupg-devel mailing list