[PYTHON-CRYPTO] Near-term projects for pycrypto

[M.-A. Lemburg]

Rich Salz wrote:
>
> > Could someone please summarize what the current state of affairs
> > is for US exports ? AFAIK, you'll have to get an official
> > "license" from the government to be able to legally export the
> > code. If so, then this should be on the list of TODOs.
>
> I just took another look at the US Gov't site, www.bxa.doc.gov.  It's
> amazingly clear right now -- they even have "Encryption" as a link on
> their main page. :)  For open source (which they call "publicly
> available"), the details are at [1].  In short, you only need to send an
> email with the URL to crypt at bxa.doc.gov.  I'm about to do so, and will
> CC this list.  (Also, Cc to exports at crypto.com so "we" have a public
> record.)

Great !

> The OpenSSL group has had expert legal advice (Dan Bernstein's EFF
> lawyer, Cindy Cohn) and they feel comfortable with US contributions as
> long as they are Cc'd to the BXA email address.

Perhaps we should put their email address on the CVS checkin
mailing list ;-)

> (Exporting *products* is almost as easy, as long as you avoid a specific
> set (Libya, et al).  We just went through the process.)

With "products" I assume you mean closed-source software, right ?

> [1] http://www.bxa.doc.gov/Encryption/PubAvailEncSourceCodeNofify.html
>         /r$

Thanks,
--
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Consulting & Company:                           http://www.egenix.com/
Python Software:                        http://www.lemburg.com/python/