> -Original Message-
> From: John Gilmore [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 25, 1999 3:55 PM
> To: Rodger, William
> Cc: William Allen Simpson; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: draft regulations?
>
I wrote:
> > Open Sou
Of course not, "click here if you aren't a terrorist" is incorrect.
"click here if you are not a citizen or national of, and this data is
not being downloaded to, Cuba, Iran, Iraq, Libya, ..." quite probably
is adequate. When I designed the initial CyberCash wallet downloading
page, it checked
Will Rodger said:
> Open Source code, believe it or not, would be essentially
> decontrolled by this proposal.
Look closer. The large print granteth and the small print taketh away.
It would be simple to exempt published encryption software from the
regulations; the Commerce Dept regs did this
Martin Minow writes:
>
> Russell Nelson wrote:
> > ... You also have to (somehow) prevent users from
> > Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria form downloading
> > the code.
>
> Ok. how am I going to do that (rhetorical question)? My Web Server is the
> module distribut
Russell Nelson wrote:
> ... You also have to (somehow) prevent users from
> Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria form downloading
> the code.
Ok. how am I going to do that (rhetorical question)? My Web Server is the
module distributed with every recent MacOS system (i.e., all
Rodger, William writes:
> Based on a conversation I had with Commerce Undersecretary William Reinsch
> last night, as well as other crypto-savvy attorneys, I think it's probably
> more useful to look at the first page of the draft. Open Source code,
> believe it or not, would be essentially de
unveiled the plan?
Simple: they hadn't thought of it.
http://www.usatoday.com/life/cyber/tech/ctg734.htm
Will
> -Original Message-
> From: William Allen Simpson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 24, 1999 11:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: d
William Allen Simpson wrote:
> What I meant is, I'd like to contribute code to FreeSWAN, or OpenSSL,
> or whatever, but the inclusion of a single line of my code will make
> the entire thing subject to EAR regulation. Worse, a single line of
> code that "looks" like a line I published will sub
According to William Allen Simpson:
> ...
> What I meant is, I'd like to contribute code to FreeSWAN, or OpenSSL,
> or whatever, but the inclusion of a single line of my code will make
> the entire thing subject to EAR regulation.
I wonder how broad is or will be "code" concept.
An interesting
"Steven M. Bellovin" wrote:
> > I was about to make a snide comment that they're just endorsing open source
> software -- but is there any definition of "other restriction"? Does the GPL
> count? Are they trying to ban any publication of anything that isn't flat-out
> public domain? And if so
>Looks like they are reinventing the GPL, except to infect
>other sources.
I think they want to make sure that if some non-US package
(openssl being the example most obvious to me) picks it up
that it doesn't suddenly become "free." So it's not the GPL,
really, but more like the old BSD license.
In article <[EMAIL PROTECTED]>,
Steven M. Bellovin <[EMAIL PROTECTED]> wrote:
>For that matter, what is "export"? Posting something to Usenet?
>Putting it up on a Web page or FTP server? The act of downloading it?
As far as I know, they haven't changed the definition of "export". Which
means t
... For that matter, what is "export"? Posting something to Usenet?
Putting it up on a Web page or FTP server? The act of downloading it?
Egad, Steve, a highest and best use for spam. I'll buy
those 300,000 e-mail addresses and send them all a copy
of the GPG source, each with another
In message <[EMAIL PROTECTED]>, William Allen Simpson writes:
> Looks like they are reinventing the GPL, except to infect other sources.
>
> (4)(i) for encryption source code (including published source code
> which is subject to proprietary commercial agreements or other
> restriction),
>From: Alan Davidson <[EMAIL PROTECTED]>
>The draft regulations are available now on CDT's web site at:
>
> http://www.cdt.org/crypto/regs112399.shtml
>
(2) Source code released under this provision remains of U.S. origin
even when used or commingled wi
15 matches
Mail list logo
