[
https://issues.apache.org/jira/browse/TIKA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580147#action_12580147
]
Jukka Zitting commented on TIKA-118:
------------------------------------
Unlike Jackrabbit, we do bundle the Bouncy Castle libraries (at least with
current TIKA-115 implementation) and have the following code snippet:
if (pdfDocument.isEncrypted()) {
try {
pdfDocument.decrypt("");
} catch (Exception e) {
// Ignore
}
}
I'm wondering if the export control stuff would be troublesome for some
downstream users. If yes, then we probably should produce alternative builds
with and without crypto code. Alternatively we could debate whether it might be
easier to just drop all the crypto dependencies and functionality.
> 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.
