I just tried it. It does not work.
Harumph. So I'm just confused. Here's the code in the current version:
match request with
"/pks/add" ->
let keytext = Scanf.sscanf (Wserver.decode body) "keytext=%s" (fun s
-> s) in
let keys = Armor.decode_pubkey keytext in
This looks right to me. It handles "keytext=<some string>"
as well as "keytext%3D<some string>". Jason's first patch
seemed to handle the cases "keytext=<some string>" and
"keytext%<some string>". Jason later proposed the following
patch:
let keytext = Wserver.decode body in
let tosser = Scanf.sscanf keytext "keytext=" (fun s -> s) in
let keytext = Str.string_after keytext 8 in
Which seems like the same thing as my most recent patch. So
what's the right behavior? Can someone explain to me what I'm
doing wrong?
Confusedly,
Ron
David
On Fri, Aug 19, 2005 at 09:22:27PM -0400, Yaron Minsky wrote:
> I still haven't heard back. Does the
> sks.dnsalias.net<http://sks.dnsalias.net>keyserver work with
> gpg+libcurl? Has any one tried it?
>
> y
>
> On 8/13/05, Yaron Minsky <address@hidden> wrote:
> >
> > I've put the server at sks.dnsalias.net <
http://sks.dnsalias.net> back up
> > (just the sks db, not the reconciliation server). Could someone try it to
> > see whether it fixes the gpg/curl bug described here?
> >
> > 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 <http://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 <http://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
<http://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/<http://keyserver.kjsl.com/%7Ejharris/>
> > > Got photons? (TM), (C) 2004
> > >
> > >
> > > _______________________________________________
> > > Sks-devel mailing list
> > > address@hidden
> > >
http://lists.nongnu.org/mailman/listinfo/sks-devel
> > >
> > >
> > >
> > >
> >
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/sks-devel
_______________________________________________
Sks-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/sks-devel