[
https://issues.apache.org/jira/browse/TIKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253407#comment-14253407
]
Tim Allison commented on TIKA-1489:
-----------------------------------
Nick persuaded me. I'm now -1 on my variant. :)
If we follow the model of PDFBox (if I understand it correctly!), we should
respect document rights in our application (tika-app), but we should let users
decide how to handle permissions in their application. As Nick points out,
Tika is more often a component in a larger process, and that larger process
should be responsible for respecting rights. We should, via metadata, enable
downstream users to decide.
I also agree with Nick that we should try to track down a standard for
representing the rights...does anything exist in XMP?
> PDF Text extraction without permission
> --------------------------------------
>
> Key: TIKA-1489
> URL: https://issues.apache.org/jira/browse/TIKA-1489
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: Tilman Hausherr
>
> In TIKA-1442 text extraction from files like 717226.pdf that don't have text
> extraction permission works. The permissions in PDF files are only enforced
> by the application (i.e. PDFBox), i.e. the text information isn't stored
> separately in encrypted form.
> PDFBox ExtractText command line does throw an exception.
> So I wonder why TIKA is able to extract text. Either TIKA or the PDFBox call
> used bypasses the permission checking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
