[
https://issues.apache.org/jira/browse/TIKA-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928108#comment-15928108
]
Tim Allison commented on TIKA-2300:
-----------------------------------
Thank you! I'll take a look soon.
bq. the change made me realise the rich metadata extracted by the PackageParser
for the compressed/inner files never finds its way back up to users through the
metadata object. Is this by design?
Via classic Tika, y, this is what happened. This is exactly why I integrated
[~jukkaz]'s and [~gagravarr]'s RecursiveParserWrapper to maintain metadata of
embedded files. Give it a try with "-J -t" from the commandline with tika-app
or try "/rmeta" if you're using tika-server.
> Can't tell if a zip file is encrypted
> -------------------------------------
>
> Key: TIKA-2300
> URL: https://issues.apache.org/jira/browse/TIKA-2300
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.14
> Reporter: Aeham Abushwashi
> Assignee: Tim Allison
> Attachments: encrypted_file.zip, TIKA-2300.patch
>
>
> When Tika processes a zip file that is protected with a password, it will
> return the list of file names within the zip but no indication (as an
> exception or in metadata) that the file is encrypted.
> From stepping through the code, I can see that the information needed to
> determine whether the archive is encrypted is available inside
> ZipArchiveEntry#getGeneralPurposeBit#usesEncryption, but needs to be relayed
> back to PackageParser somehow
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)