Return-Path: <push>
Return-Path: owner-openssl-dev@openssl.org
Received: from opensource.ee.ethz.ch (opensource-01.ee.ethz.ch [129.132.7.153])
	by brev.stacken.kth.se (8.9.3/8.9.3) with ESMTP id SAA01565
	for <levitte@stacken.kth.se>; Thu, 16 Mar 2000 18:22:41 +0100 (MET)
Received: by en5.engelschall.com (Sendmail 8.9.2) for openssl-dev-L
	id SAA03196; Thu, 16 Mar 2000 18:00:25 +0100 (MET)
Received: by en5.engelschall.com (Sendmail 8.9.2) via ESMTP for <openssl-dev@openssl.org>
	from eastwood.aldigital.algroup.co.uk id SAA03167; Thu, 16 Mar 2000 18:00:07 +0100 (MET)
Received: from freeby.ben.algroup.co.uk (freeby.ben.algroup.co.uk [193.133.15.6]) by eastwood.aldigital.algroup.co.uk (8.8.8/8.6.12) with ESMTP id QAA07961; Thu, 16 Mar 2000 16:58:51 GMT
Received: from algroup.co.uk (naughty.ben.algroup.co.uk [193.133.15.107]) by freeby.ben.algroup.co.uk (8.6.12/8.6.12) with ESMTP id QAA07782; Thu, 16 Mar 2000 16:59:02 GMT
Message-ID: <38D112C4.D3CD6897@algroup.co.uk>
Date: Thu, 16 Mar 2000 16:58:44 +0000
From: Ben Laurie <ben@algroup.co.uk>
Organization: A.L. Group plc
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
MIME-Version: 1.0
To: Eben Moglen <moglen@columbia.edu>
CC: Ulf =?iso-8859-1?Q?M=F6ller?= <ulf@fitug.de>, openssl-dev@openssl.org,
        rms@gnu.org, members@apache.org, php-dev@lists.php.net
Subject: Re: [Eben Moglen <moglen@columbia.edu>] Re: US crypto export 
 restrictionsand GNU (fwd)
References: <Pine.WNT.4.21.0003090021290.-31249-110000@vaio.php.net>
		<38CDFEEC.9C9159BD@algroup.co.uk>
		<200003150456.VAA29971@aztec.santafe.edu>
		<E12V7R4-0002c0-00@old.law.columbia.edu>
		<38CFC136.8B8873FE@algroup.co.uk>
		<E12VIgR-00030m-00@old.law.columbia.edu>
		<20000316014140.A604@rho> <E12VUq1-000371-00@old.law.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-openssl-dev@openssl.org
Precedence: bulk
Reply-To: openssl-dev@openssl.org
X-Sender: Ben Laurie <ben@algroup.co.uk>
X-List-Manager: OpenSSL Majordomo [version 1.94.4]
X-List-Name: openssl-dev

Eben Moglen wrote:
> In the worst case analysis, components exported
> now might subsequently become non-exportable in the event that
> regulations in the US become more restrictive.  No one would be
> subject to prosecution or interference as a result of export occurring
> before the change in regulations (that's a matter of constitutional
> law in the US), but all subsequent development of those components
> would then have to occur somewhere other than here.  No code not
> originally developed in the US would be subject to this tightened
> regulatory environment, unless such code were "in" the US, in which
> case the particular copy that was "in" the US wouldn't be able to
> leave again--a restriction which makes no difference.

Perhaps I'm failing to understand here ... you say "No code not
originally developed in the US would be subject to..." but sure we're
talking about code that _was_ developed inside the US.

Cheers,

Ben.

--
SECURE HOSTING AT THE BUNKER: http://www.thebunker.net/hosting.htm

http://www.apache-ssl.org/ben.html

Coming to ApacheCon Europe? http://ApacheCon.Com/
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           majordomo@openssl.org