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 URL to obtain the source code) to > [EMAIL PROTECTED] and [EMAIL PROTECTED] Please see Export Administration > Regulations Section 740-13(e), and > http://bxa.doc.gov/encryption/PubAvailEncSourceCodeNofify.html I know this but reading the mailing list archive of openssl-dev@openssl.org, it looks like some members of the OpenSSL community already did this and I hoped to simply get the CCATS number of a release. Obviously we can also send emails to [EMAIL PROTECTED] and [EMAIL PROTECTED] with the OpenSSL source code we use for our product but I thought it would be better to have this handled centrally and only once. > Its ECCN would normally be 5D002, but since it's publicly-available > source code it is under exemption TSU, provided the notification > requirements are met. Or so it reads to me. OK. Regards, Uwe Girlich -- Dr. Uwe Girlich email: [EMAIL PROTECTED] Philosys Software GmbH www: www.philosys.de Edisonstrasse 6 phone: +49 89 321407-44 D-85716 Unterschleissheim fax: +49 89 321407-12 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
