Why do we want to have another ad-hoc HTTP implementation? Wouldn't a small *CGI script be good enough?
Joerg On Mon, Mar 01, 2010 at 07:41:57AM +0000, Alistair G. Crooks wrote: > Module Name: src > Committed By: agc > Date: Mon Mar 1 07:41:57 UTC 2010 > > Added Files: > src/crypto/external/bsd/netpgp/dist/src/hkpd: Makefile hkpd.c hkpd.h > main.c > > Log Message: > add an embryonic httpd key server (hkpd) to netpgp. this is based on the > discontinued draft for hkp servers, in lieu of any official rfc. > > the post method for adding keys to the server has not been implemented. > not until i've gone through all of the implications, anyway. > > hkp servers serve up pgp public keys over http. the default port is 11371, > but it can be any port, specifiable at run time. whilst this hkpd will > return valid html to browsers, it is aimed at the ''machine readable'' > side, using the ''&options=mr'' option to the http get string. > > this hkpd server will get hooked into the build at a later date. > > > To generate a diff of this commit: > cvs rdiff -u -r0 -r1.1 src/crypto/external/bsd/netpgp/dist/src/hkpd/Makefile \ > src/crypto/external/bsd/netpgp/dist/src/hkpd/hkpd.c \ > src/crypto/external/bsd/netpgp/dist/src/hkpd/hkpd.h \ > src/crypto/external/bsd/netpgp/dist/src/hkpd/main.c > > Please note that diffs are not public domain; they are subject to the > copyright notices on the relevant files.
