use PGP for http encryption instead!
i don't mean to be extremely brash, but couldn't one use PGP to provide encrypted communication with the web. granted initially everyone with a browser would need there own key to communicate in an encrypted way - at least until such keys could be generated on the fly. since the http "client" format resembles rfc821 message headers and a body, one could easily use a "hal" remailer type "Encrypted: PGP" header line plus hash marks "::" to reassemble a compatible http client command. The same could be done on the server side. -george --- libgpmx@gsusgi2.gsu.edu (finger for PGP public key or use MIT keyserver) George P. Magiros Georgia State University Pullen Library PGP fingerprint of 59069039: D6 76 D4 FC 9B 25 6E DD DD 81 58 06 7B CD 03 AE
-----BEGIN PGP SIGNED MESSAGE----- On Thu, 17 Aug 1995, George P. Magiros wrote:
i don't mean to be extremely brash, but couldn't one use PGP to provide encrypted communication with the web. granted initially everyone with a browser would need there own key to communicate in an encrypted way - at least until such keys could be generated on the fly.
since the http "client" format resembles rfc821 message headers and a body, one could easily use a "hal" remailer type "Encrypted: PGP" header line plus hash marks "::" to reassemble a compatible http client command. The same could be done on the server side.
As far as I understand, no. 1) you can't export PGP. 2) even though it's out there, making software with hooks for PGP is equally bad in the eyes of the NSA. There wa some talk on alt.internet.media-coverage (and the thread is being crossposted all over the place) about mosaic having to remove PGP hooks before the NSA would let them export. 3) Frankly, I don't necessarily trust something that plays with my personal stuff if I can't access the source code to make sure it's not messin' with it :-) -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP Signed with PineSign 2.2 iQCVAwUBMDPo2DokqlyVGmCFAQH9wAP9EB9rdvCAu32ULCUqO6YE4eKSpn4499n8 S/FFeSD7QqRKRzDFs/FsWPqVJfgeD05QJRysrCBRwZTh8//jXBaiLJ6IhqG18YsE oQq7bFXTEk9BmFcjGljhaLYX548qSmkZCFyBa5LNG96f4Lpj3kOE02BmWNRcCT3Y U7kCk1btxcY= =RVSJ -----END PGP SIGNATURE----- ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ Finger for Geek Code Info <=> Finger for PGP Public Key \/ / -=-=-=-=-=- -=-=-=-=-=- \/ http://krypton.mankato.msus.edu/~hayden/Welcome.html -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GED/J d-- s:++>: a-- C++(++++) ULU++ P+ L++ E---- W+(-) N++++ o+ K+++ w--- O- M+ V-- PS++>$ PE++>$ Y++ PGP++ t- 5+++ X++ R+++>$ tv+ b+ DI+++ D+++ G+++++ e++ h r-- y++** ------END GEEK CODE BLOCK------
| "George P. Magiros" writes: | > i don't mean to be extremely brash, but couldn't one use PGP to provide | > encrypted communication with the web. | | You ought to read up on S-HTTP, the expert on said protocol being our | very own Eric Rescorla... PGP support was taken out of the latest SHTTP draft, apparently because no one had implemented it. Should someone build a libSHTTP with PGP support, I suspect it would get back into the spec. Adam -- "It is seldom that liberty of any kind is lost all at once." -Hume
participants (4)
-
adam@bwh.harvard.edu -
George P. Magiros -
Perry E. Metzger -
Robert A. Hayden