Subject: [Classpathx-crypto] export issues

From: "Raif S. Naffah" <[email-masked]>
Date: Fri, 02 Aug 2002 06:15:18 +1000

it was brought to my attention that there may be some export issues 
regarding the distribution of gnu.crypto code.

the concern is related to the fact that: although most of the developers 
reside outside the USA, the gnu.crypto project is officially distributed 
(a) by the FSF (b) from the USA.  is anybody aware of any limitation or 
legal issues that should be addressed before we release/distribute our 
code?  should an FSF legal person be consulted on this?

cheers;
rsn

---

From: Nic Ferrier <[email-masked]>
Date: 01 Aug 2002 22:26:42 +0100

> code?  should an FSF legal person be consulted on this? 

I don't think there are any issues anymore.

Can you tell me (privately please) who the developers for the project
are (in the past as well as now) and where they reside?

I will consult the relevant people for you.

Nic

---

From: Casey Marshall <[email-masked]>
Date: Thu, 1 Aug 2002 15:23:00 -0700 (PDT)

> code?  should an FSF legal person be consulted on this?

(Caveat: IANAL)

I think, according to Export Administrations Regulations section 740.13(e),
open-source encryption software can be exported without regulation, as
long as (1) it is not made available for download to Cuba, Iran, Iraq,
Libya, North Korea, Sudan or Syria and (2) you notify the Bureau of
Industry and Security at <[email-masked]> before it is made publicly
available.

Want to sift through United States export regulations? Look at

	http://w3.access.gpo.gov/bis/ear/ear_data.html

Part 740, which appears to be the relevant one, is at:

	http://w3.access.gpo.gov/bis/ear/{pdf,txt}/740.{pdf,txt}

-- 
Casey Marshall < [email-masked] > http://metastatic.org/