keyserver sending problems

Fri May 4 22:55:01 CEST 2001

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4 May 2001, Josh Huber wrote:

> Andrew McDonald <andrew at mcdonald.org.uk> writes:
>
> > I'm currently having problems with --send-key also. --recv-key is OK.
> > This is using an unchanged copy of 1.0.5 (and also the Debian 1.0.5-1
> > package).
> >
> > With --send-key I get the error:
> > gpg: failed sending to `horowitz.surfnet.nl': status=400
> > This does not depend on the keyserver I use. 1.0.4 works OK.
> >
> > Adding a -vvvv I also see:
> > <HEAD><TITLE>400 Bad Request</TITLE></HEAD><BODY></BODY>
> >
> > I haven't delved any deeper at the moment.
>
> Yep, I'm having the same problem right now.  I can't --send-key with
> any keyserver (that I've tried) with stock 1.0.5.

Yeah,  looks like 1.05 has an extra line feed after the request header
which is throwing off the keyservers. I'll see if I can't write a quick
patch...

1.0.5:

POST /pks/add HTTP/1.0

Content-Length: 26040
[keytext=url encoded ascii armored key]

Should be (like 1.0.4):

POST /pks/add HTTP/1.0
Content-Length: 26040

[keytext=url encoded ascii armored key]

		- VAB

- ---
V. Alex Brennen    [vab at cryptnet.net]
[http://www.cryptnet.net/people/vab/]
  F A R  B E Y O N D  D R I V E N !
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: Made with pgp4pine 1.75-6

iD8DBQE68v0A+pIJc5kqSz8RAk8OAJ9xh262EP0IQmstLGMWaougbrrZ5ACgqD5A
DtPeQ/AUBlCPVr8DcpfiLf4=
=IxEm
-----END PGP SIGNATURE-----