accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1714) Do we need to take care of crypto based export control policy?
Date Wed, 09 Oct 2013 16:42:44 GMT


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."


> Do we need to take care of crypto based export control policy?
> --------------------------------------------------------------
>                 Key: ACCUMULO-1714
>                 URL:
>             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:
> 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

View raw message