W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 1998

SSL

From: Jamie Fox <jfox@fenix2.dol-esa.gov>
Date: Tue, 24 Nov 1998 12:26:42 -0500
To: <w3c-wai-ig@w3.org>
Message-ID: <000001be17cf$9bc37660$dbc3c8c7@jfox.dol-esa.gov>
I am confused why the US encryption laws would be a barrier.  Couldn't lynx
just use 64 bit encryption like the normal version of Netscape and Internet
Explorer do?  It is only the strongly encrypted (128 bit) that you have to
promise not to give to foreign drug dealers.

-Jamie

-----Original Message-----
From:	w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf
Of Chris Maden
Sent:	Tuesday, November 24, 1998 12:10 PM
To:	w3c-wai-ig@w3.org
Subject:	Re: information access at chicago transit authority

[Jamal Mazrui]
> I'm fairly sure Kelly Pierce is using Lynx 2.8.
> I also thought it supported SSL connections, but when my ISP
> (Smartnet) upgraded to this version, I discovered SSL support is
> lacking.  Perhaps there is some configuration setting to turn it
> on -- if so, I'd like to know about it.

Lynx *can* use SSL, but doesn't in the default distribution.  Because
SSL can not be exported under the US's bizarre encryption laws, SSL-
enabled Lynx couldn't be placed on a public FTP server.

There are places where you can request SSL patches for Lynx (start at
<URL:http://lynx.browser.org/>), but you then have to compile Lynx
yourself.  I had some trouble doing this with Lynx 2.8.

-Chris
--
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
Received on Tuesday, 24 November 1998 12:26:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:40 GMT