-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Geoffrey Irving wrote:
> On Sep 12, 2013, at 10:44 AM, John Clizbe <[email protected]> wrote:
>>
>> I was going to reply on [sks-devel], but this is as good a place as
>> any. The patch to wserver.ml is fairly straightforward. But I'm curious
>> as to why wserver.mli was patched to remove the interface spec for
>> send_result.
>
> That was just general paranoia about generic looking functions with open
> CORS interfaces. It would be fine (better?) to leave it public, but if
> so it needs to be documented so that some unsuspecting future user
> doesn't copy and paste code for some other purpose and generate a
> security hole. I suppose I actually already wrote the required comment
> in the .ml, so I probably should have just copied the comment to the
> .mli.
OK, I left the interface spec as it was and just imported the patch against
wserver.ml
>> BTW, I can probably give you keyserver.gingerbear.net and
>> sks.keyservers.net to test against
>
> Awesome, thanks! Let me know when I should give it a try.
Go ahead. Report buggy things at the gingerbear addr below
- --
John P. Clizbe Inet: John (a) Gingerbear DAWT net
SKS/Enigmail/PGP-EKP or: John ( @ ) Enigmail DAWT net
FSF Assoc #995 / FSFE Fellow #1797 hkp://keyserver.gingerbear.net or
mailto:[email protected]?subject=HELP
Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
Comment: Be part of the £33 ECHELON -- Use Strong Encryption.
Comment: It's YOUR right - for the time being.
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iF4EAREIAAYFAlIyGOQACgkQ614Z89ZWmCULbQD/Qo96HtbnVfnAH2sxAPMzmtr6
5muIS5TWNO59gsHKxb4A/15g/hqwJRNu7WUPoMz91V2xNrI4MKMin1qqTEC1Se0m
=cIpy
-----END PGP SIGNATURE-----
_______________________________________________
http://openpgpjs.org
