You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Parth Chandra (JIRA)" <ji...@apache.org> on 2017/06/02 20:06:04 UTC
[jira] [Created] (LEGAL-312) Crypto regulations not being satisfied
Parth Chandra created LEGAL-312:
-----------------------------------
Summary: Crypto regulations not being satisfied
Key: LEGAL-312
URL: https://issues.apache.org/jira/browse/LEGAL-312
Project: Legal Discuss
Issue Type: Question
Reporter: Parth Chandra
While researching requirements for supporting SSL in Apache Drill, I realized that Drill has had support for HTTPS via the Jetty Web Server for several releases. Also, in the current source tree, a recent commit has added support for SASL with encryption (this has not been included in a Drill release yet). Per my understanding of crypto regulations [1], we should have reported this before committing the code.
Now that this is already committed, what action should we take?
It is given, I presume, that we should take all the required actions, i.e. update the exports page, inform the US government and add to the project readme. Should we be doing anything else?
[1] http://www.apache.org/dev/crypto.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org