accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-1714) Do we need to take care of crypto based export control policy?
Date Fri, 25 Oct 2013 21:50:32 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Vines resolved ACCUMULO-1714.
----------------------------------

    Resolution: Fixed
      Assignee: John Vines

Apache Accumulo has been added to the apache exports page ( http://www.apache.org/licenses/exports/
), USG has been notified, and we now have the requisite information in our README files.

> 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
>            Assignee: 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)

Mime
View raw message