1998-01-11 - Re: Adding SSL to things

Header Data

From: Bill Stewart <bill.stewart@pobox.com>
To: Ryan Lackey <rdl@MIT.EDU>
Message Hash: f764e47071f3befb2336d1448a486fc1fc09ce7adc79cb3a16351ecb7ecafee0
Message ID: <3.0.5.32.19980111132145.00883540@popd.ix.netcom.com>
Reply To: <“Raymond D. Mereniuk”’s message of Sat, 10 Jan 1998 20:05:03 +0000>
UTC Datetime: 1998-01-11 21:42:10 UTC
Raw Date: Mon, 12 Jan 1998 05:42:10 +0800

Raw message

From: Bill Stewart <bill.stewart@pobox.com>
Date: Mon, 12 Jan 1998 05:42:10 +0800
To: Ryan Lackey <rdl@MIT.EDU>
Subject: Re: Adding SSL to things
In-Reply-To: <"Raymond D. Mereniuk"'s message of Sat, 10 Jan 1998 20:05:03 +0000>
Message-ID: <3.0.5.32.19980111132145.00883540@popd.ix.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain



At 06:11 AM 1/11/98 -0500, Ryan Lackey wrote:
>Does anyone know of a way I can take a web server, say AOLserver, which
>does not support useful SSL, and also does not distribute source, and
>retrofit a useful 128-bit SSL implementation to it?  It has a C API, but
>I haven't looked at the API enough to see if I could do it within the API.
>Are there any proxies which could be stuck between the insecure server
>and the user (preferably with an ssh link between the servers) which could
>provide SSL proxy service?  It seems like this should be trivial to do,
>but I haven't tried yet, and I want to have some reedeming value for this
>post.]

Why not just get a server that _does_ have useful SSL support,
like Apache-SSL (for non-US freeware) or Stronghold (for US commercial use)?
There are workarounds out there for undersecure clients,
like SafePassage and some German Java applet, but that's the easy side.


				Thanks! 
					Bill
Bill Stewart, bill.stewart@pobox.com
PGP Fingerprint D454 E202 CBC8 40BF  3C85 B884 0ABE 4639






Thread