From xemacs-m  Sat Aug  2 10:33:17 1997
Received: from firewall2.Lehman.COM (firewall.Lehman.COM [192.147.65.67])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA09321
	for <xemacs-beta@xemacs.org>; Sat, 2 Aug 1997 10:33:16 -0500 (CDT)
Received: from relay.messaging-svcs2.lehman.com by firewall2.Lehman.COM (8.8.6/8.6.12) id LAA25007; Sat, 2 Aug 1997 11:33:10 -0400 (EDT)
Received: from cfdevx1.lehman.com by relay.messaging-svcs2.lehman.com (8.8.5/8.8.5) id LAA02396; Sat, 2 Aug 1997 11:32:39 -0400 (EDT)
Received: from localhost by cfdevx1.lehman.com (4.1/Lehman Bros. V1.6)
	id AA05523; Sat, 2 Aug 97 11:32:13 EDT
Message-Id: <9708021532.AA05523@cfdevx1.lehman.com>
Reply-To: Rick Campbell <rickc@lehman.com>
X-Face: #<@""pDMxa>Mr$Wp[^l7e1RwB6]&7pRp,f=|)6y5?t45X$y(xx.x^?k~;-d>s:SL86Qt82U
 'M!RC3LrDvD/LjiYdGO!:\/\qx?YabgGC9%xw5%0-W05LRvyu9vB9TYk%5PN|C*0WgrXD-L0'g3j;h
X-Windows: The joke that kills.
Organization: Lehman Brothers Inc.
From: Rick Campbell <rickc@lehman.com>
To: Jin Choi <jsc@w3health.com>,
        "Patrick J. LoPresti" <patl@catfish.lcs.mit.edu>
Cc: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Mailcrypt HTTP key fetching vs. firewalls
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="pgp-sign-Multipart_Sat_Aug__2_11:31:42_1997-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit
Date: Sat, 02 Aug 1997 11:32:11 -0400
Sender: rickc@lehman.com

--pgp-sign-Multipart_Sat_Aug__2_11:31:42_1997-1
Content-Type: multipart/mixed;
 boundary="Multipart_Sat_Aug__2_11:31:42_1997-1"
Content-Transfer-Encoding: 7bit

--Multipart_Sat_Aug__2_11:31:42_1997-1
Content-Type: text/plain; charset=US-ASCII

This is based on mailcrypt as it is included in XEmacs 19.15.  If
fetching keys via HTTP has already been adjusted to handle firewalls,
please ignore this message.

Mailcrypt's mc-pgp-fetch-from-http assumes that it can do an
open-network-stream to an arbitrary site.  Behind (at least some kinds
of) firewalls, this fails.  Since W3 already handles firewall issues
quite nicely, I wrote a fetch method that piggy-backs off of it.

The direct dependencies introduced by this function are on
url-retrieve (url.el, lines 1992-2008) and on url-working-buffer which
is used by url-retrieve.

			Rick


--Multipart_Sat_Aug__2_11:31:42_1997-1
Content-Type: text/plain; charset=US-ASCII

(defun mc-pgp-fetch-from-w3 (id)
  (let (buf)
    (unwind-protect
	 (progn
	   (message "Fetching %s via HTTP to %s..."
		    (or (cdr id) (car id)) mc-pgp-keyserver-address)
	   (setq buf (generate-new-buffer " *mailcrypt temp*"))
	   (let ((url-working-buffer buf))
	     (url-retrieve (concat "http://"
				   mc-pgp-keyserver-address
				   (format mc-pgp-keyserver-url-template
					   (or (cdr id) (car id))))))
	   (mc-pgp-buffer-get-key buf))
      (if buf (kill-buffer buf)))))

--Multipart_Sat_Aug__2_11:31:42_1997-1--

--pgp-sign-Multipart_Sat_Aug__2_11:31:42_1997-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP MESSAGE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBM+NS9ltTztlqB385AQHpuwP+OpGr/PZE0o2CmZwhWnHkv8dCFCWi30Bk
oG4vlNx8T1sVr8OBqq9uAktYuzm3eur9g/zLxnKyzWJSvDg5aJtis8IJkcZnkUOx
NJVVOHLpzWu04ZpsKjTfJoQ4SgUbEFTwasSePWQQlDXtGmxrD+ZbQXb+02FY/5MD
TsDgppQZVCg=
=DWcU
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Sat_Aug__2_11:31:42_1997-1--

