RE: Crypt::OpenSSL Proposal
Christian Gilmore (cgilmore@research.att.com)
Fri, 26 Feb 1999 09:48:50 -0500
This does mean, though, that you have the SSL-served pages in cleartext
before sending them back to the client. This is an interesting policy to
choose. Puts you on the hook, as you now have information that is ideally
intended solely for the client.
Christian
-----------------
Christian Gilmore
Senior Technical Staff Member
AT&T Labs IP Technology, Florham Park
cgilmore@research.att.com
http://www.research.att.com/info/cgilmore
> -----Original Message-----
> From: libwww-perl-request@ics.uci.edu
> [mailto:libwww-perl-request@ics.uci.edu]On Behalf Of James Han
> Sent: Friday, February 26, 1999 12:34 AM
> To: HYATTDJ@sce.com; joshua@chamas.com; libwww-perl@ics.uci.edu;
> mi@alma.ch
> Subject: RE: Crypt::OpenSSL Proposal
>
>
> Hi,
>
> I just want to suggest an alternative solution here for
> "desparate audience":
> using a web proxy server.
>
> I've configured Squid and Netscape proxy server to support
> HTTPS protocol(not
> just CONNECT) then run a regular Perl script with lwp to get
> pages from
> secure web servers. This doesn't require any patch on your
> perl installation.
>
> Of course this implies installing and configuring a proxy
> server is easier
> than installing SSL patches for perl :-)
>
> Hope this info is helpful and not off the subject too far.