Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DEFF510E02 for ; Wed, 9 Oct 2013 16:42:54 +0000 (UTC) Received: (qmail 10918 invoked by uid 500); 9 Oct 2013 16:42:51 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 10664 invoked by uid 500); 9 Oct 2013 16:42:47 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 10583 invoked by uid 99); 9 Oct 2013 16:42:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Oct 2013 16:42:44 +0000 Date: Wed, 9 Oct 2013 16:42:44 +0000 (UTC) From: "Billie Rinaldi (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1714) Do we need to take care of crypto based export control policy? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790597#comment-13790597 ] Billie Rinaldi commented on ACCUMULO-1714: ------------------------------------------ Thanks for starting that discussion. What I gather from your thread as well as [1] is that we are still using the process outlined on dev/crypto.html. Also, I note that no one replied to your question as to whether ACCUMULO-998 needs to follow the policy as well, but someone states on the earlier thread "Note the threshold is -using- that encryption mechanism, not that your code -implements- that cryptographic code." [1]: http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201306.mbox/%3C87ehc6b355.fsf@v35516.1blu.de%3E > Do we need to take care of crypto based export control policy? > -------------------------------------------------------------- > > Key: ACCUMULO-1714 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1714 > Project: Accumulo > Issue Type: Bug > Reporter: John Vines > Priority: Blocker > Fix For: 1.6.0 > > > This came up in ACCUMULO-1009, but also may affect ACCUMULO-998. > Related info: > https://issues.apache.org/jira/browse/TIKA-118 > http://www.apache.org/licenses/exports/ > http://markmail.org/message/jduwmahz7nfcrzw6 > http://www.apache.org/dev/crypto.html > The dev/crypto.html is from the last version in 2010, which has changed based on some legal-discuss items I read. > Initial thoughts are: > ACCUMULO-998 is fine because we do not ship ANY crypto modules with that, just an interface to use them > ACCUMULO-1009 is not fine IF we bundle bouncycastle in with us. -- This message was sent by Atlassian JIRA (v6.1#6144)