[
https://issues.apache.org/jira/browse/TIKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377966#comment-14377966
]
Tim Allison commented on TIKA-1489:
-----------------------------------
To close the loop on this, there are 2,784 pdfs out of 231,229 pdfs in govdocs1
that do not allow extraction. Thank you, Tilman!
> 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
> Fix For: 1.8
>
> Attachments: TIKA-1489_v1.patch,
> testPDF_no_extract_no_accessibility_owner_empty.pdf,
> testPDF_no_extract_no_accessibility_owner_user.pdf,
> testPDF_no_extract_yes_accessibility_owner_empty.pdf,
> testPDF_no_extract_yes_accessibility_owner_user.pdf
>
>
> 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)
