El Lunes 10 Abril 2006 23:37, Manuel Naranjo escribió:
Aquí hay más datos sobre la regulación de EEUU, Cryto y la exportación de criptografía. http://www.gnu.org/software/gnu-crypto/mail/classpathx-crypto.mbox On Fri, 2 Aug 2002, Raif S. Naffah wrote: > 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? > (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 PROTECTED]> 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} -- Sebastián D. Criado - scriado{en}ciudad.com.ar L.U.G.R.o - http://www.lugro.org.ar GNU/Linux Registered User # 146768 ------------------------------------------------------------------- "Si el Universo fuera un programa estaría hecho en C, y correría sobre un sistema UNIX" Anónimo.
pgpIeMs6mRKh2.pgp
Description: PGP signature
