Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
From: David Nalley <david@gnsa.us>
Date: Wed, 12 Sep 2012 02:35:29 -0400
Message-ID: 
 <CAKprHVbDeE-f8wHs5ahSFiT2gov2V61UOKfcvtnQi36hXz6+6Q@mail.gmail.com>
Subject: Crypto export filings for Apache CloudStack (incubating)
To: legal-discuss@apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi folks,

The crypto page [1] advises me to start a conversation here regarding
export control filings for projects that contain or depend on crypto.

A bit of background - CloudStack's source code itself doesn't contain
any crypto, but does depend and make use of various pieces of
cryptography including things like ssh, MySQL encryption functions,
java crypto libraries like bouncy castle, VPN software, etc.

I do have a copy of EAR Part 742 Supplement 6, which was filed
approximately a year ago for the open source project & product that
Cloud.com shipped - several new issues relating to  encryption have
arisen (new VPN types, default use of database encryption, etc.) since
that filing, but perhaps it serves as a good base.

In short,
What is the ASF's process for getting export filings taken care of?

Thanks,

--David
[1] http://www.apache.org/dev/crypto.html

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org