On 20 May 2016 at 08:53, Benedikt Ritter <brit...@apache.org> wrote: > b. "Open Cryptographic Interface" items. [740.17(b)(2)] > looks correct. But this is just my lucky guess.
I'm struggling to find the official definition of "OCI", but I think it's this: https://www.bis.doc.gov/index.php/forms-documents/doc_view/838-772 > (Open cryptographic interface - A mechanism which is designed to allow a > customer or other party to insert cryptographic functionality without > the intervention, help or assistance of the manufacturer or its agents > (i.e., manufacturer's signing of cryptographic code or proprietary > interfaces). If the cryptographic interface implements a fixed set of > cryptographic algorithms, key lengths or key exchange management > systems, that cannot be changed, it will not be considered an "open" > cryptographic interface. All general application programming interfaces > (i.e., those that accept either a cryptographic or non-cryptographic > interface, but do not themselves maintain any cryptographic > functionality) will not be considered "open" cryptographic interfaces > either.) Are you sure this is the case for commons-crypto? I thought we only supported JCE encryption and Open SSL encryption. If it is the case it seems we have to submit a formal "encryption classification request", and export would be more restricted on which countries are permitted. See: https://www.bis.doc.gov/index.php/policy-guidance/encryption/classification -- Stian Soiland-Reyes Apache Commons, Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
