OpenSSL, as open-source software, falls under export exemption TSU.
Reference 15 CFR Parts 734, 740, 742, 770, 772, and 774.
This information is taken from
http://www.epic.org/crypto/export_controls/regs_1_00.html:
3. Also in ยง740.13, to, in part, take into account the open source
approach to
PLEASE NOTE: I am not a lawyer. If you need the opinion of one, ask
one. However, a clear reading appears to state that you just have to
send a copy of the source code (or a URL to obtain the source code) to
[EMAIL PROTECTED] and [EMAIL PROTECTED] Please see Export Administration
Regulations
Hello!
On Tue, Mar 07, 2006 at 06:13:22AM -0700, Kyle Hamilton wrote:
PLEASE NOTE: I am not a lawyer. If you need the opinion of one, ask one.
I asked one of the export experts of Siemens.
However, a clear reading appears to state that you just have to
send a copy of the source code (or a
In message [EMAIL PROTECTED] on Tue, 7 Mar 2006 15:07:37 +0100, Dr. Uwe
Girlich [EMAIL PROTECTED] said:
Uwe.Girlich I know this but reading the mailing list archive of
Uwe.Girlich openssl-dev@openssl.org, it looks like some members of
Uwe.Girlich the OpenSSL community already did this and I
On 3/7/06, Dr. Uwe Girlich [EMAIL PROTECTED] wrote:
Hello!
On Tue, Mar 07, 2006 at 06:13:22AM -0700, Kyle Hamilton wrote:
PLEASE NOTE: I am not a lawyer. If you need the opinion of one, ask one.
I asked one of the export experts of Siemens.
Cool. Just tell the export experts to read the
Hello!
I'm working for Siemens and we deliver OpenSSL 0.9.8 as part of a big Telco
product. To export this whole product, we need ECCN numbers and possible TSU
exceptions with CCATS numbers for all components and as such also for OpenSSL.
Browsing through your mailing archive, I found mails like
