Re: [Sks-devel] Re: SKS v. unknown HTTP headers (was: Re: IPv6 failover?)

[Yaron Minsky]

The new patch behaves differently from Jason's original patch, as far
as I can tell.  Jason's patch assumed the structure was
"keytext=<key>" or "keytext%<key>".  My current uses
Wserver.decode, which effectively requires either "keytext=<key>"
or "keytext%3D<key>".  Which behavior is actually correct?

y

On 8/10/05, Jason Harris <address@hidden> wrote:

On Wed, Aug 10, 2005 at 10:53:35AM +0200, Dinko Korunic wrote:
> On Tue, Aug 09, 2005 at 09:54:07PM -0400, Yaron Minsky wrote:

> > mentioned. Could a couple people try out the latest release and see if it
> > seems OK? If no one complains over the next few days, I will put out a new
>
> Seems to be working fine on pks.aaiedu.hr.

Are you sure?  Sending a key using GPG 1.4.2+libcurl to my (test) SKS
server with Yaron's latest patches now breaks with:

  Error handling request (POST,/pks/add,[+accept:*/*+content-length:45716+content-type:application/x-www-form-urlencoded+expect:100-continue+host: skylane.kjsl.com:21371]): Failure("Error while decoding ascii-armored key:  text terminated before reaching PGP public key header line")

Interestingly, gpg-1.4.3-cvs reports:

  gpgkeys: HTTP post error 22: Failed to connect to 2001:1868:205:1::100: Connection refused

(even though SKS confirms contact and generates the above error)
while gpg-1.4.2 reports:

  gpgkeys: HTTP post error 22: The requested URL returned error: 500

Your server is also bouncing keys from gpg-1.4.2 and gpg-1.4.3-cvs:

  gpg: sending key ... to hkp server pks.aaiedu.hr
  gpgkeys: HTTP post error 22: The requested URL returned error: 500

Both GPGs are linked with curl-7.14.0.

--
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
address@hidden _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004


_______________________________________________
Sks-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/sks-devel