[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV SSL for Lynx 2.8

From: Philip Webb
Subject: Re: LYNX-DEV SSL for Lynx 2.8
Date: Tue, 10 Mar 1998 20:14:43 -0500 (EST)

980309 Scott McGee wrote: 
> The US ITAR/(what is it now, EAR?) regulations have been interpreted
> as prohibiting the distribution of software with SSL _HOOKS_ in it.
> I for one would feel very uncomfortable to see it in Lynx
> (as much as I would love to be able to) and would likely have to deny
> download access to Lynx source from our site (not a good thing to consider!)
> to protect the college if SLL hooks were included.
> I noticed in the Netscape Public License, that they have removed all SSL
> from the code that will be made publicly availible,
> persumably for similar reasons.
> Again, let me emphasize, that I could not continue to support public access
> to the Lynx Source from if SSL hooks are added to the code.
fully understood & sympathised with here!
my impression is that US law enforcement is much more ruthless
than Europeans & Canadians are used to:
the Boston Nanny & Connecticut Teenager cases are obvious examples (to us),
let alone the queues of people being executed after  >= 15 yrs .
so no-one should ask Americans to take any risks handling Lynx-SSL.

Canadians are in a grey zone, since only vague regulations apply,
but the paranoid brigade can easily appear out of nowhere on our campuses,
whatever the true legal risks involved.
there have been Australian & Netherlands sites mentioned
as willing & able to ignore the US restrictions & there may be others.
there may be copyright or ethical questions to be raised,
but it's open to non-US members of the Lynx co-op to raise their e-hands
if they would like to offer support for Lynx-SSL,
when further discussion towards a consensus could take place.

SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto

reply via email to

[Prev in Thread] Current Thread [Next in Thread]