You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2008/03/18 23:24:24 UTC

[jira] Commented: (TIKA-118) Bouncycastle binaries requires US exports regulation compliance

    [ https://issues.apache.org/jira/browse/TIKA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580143#action_12580143 ] 

Hoss Man commented on TIKA-118:
-------------------------------

in light of this thread on legal-discuss...

http://markmail.org/message/jduwmahz7nfcrzw6

...does Tika really need a crypto notice?  Is Tika's use of PDFBox really any different then Jackrabbit's?

My understanding from reading that thread is that as long as Tika (or any Project "X") does not contain any code to specifically use PDFBox for the purpose of encryption, then X doesn't need a crypto notice -- even if PDFBox is included in distributions of X.  The only reason X would need a crypto notice for using PDFBox is if it directly includes the BouncyCastle libraries in it's distributions.

correct?

> Bouncycastle binaries requires US exports regulation compliance
> ---------------------------------------------------------------
>
>                 Key: TIKA-118
>                 URL: https://issues.apache.org/jira/browse/TIKA-118
>             Project: Tika
>          Issue Type: Task
>    Affects Versions: 0.2-incubating
>            Reporter: Bertrand Delacretaz
>            Assignee: Jukka Zitting
>             Fix For: 0.2-incubating
>
>
> See http://markmail.org/message/jduwmahz7nfcrzw6 , we need to take care of some US export regulations paperworks before shipping the binary package created in TIKA-115.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.