[ https://issues.apache.org/jira/browse/TIKA-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830490#comment-17830490 ]
ASF GitHub Bot commented on TIKA-4219: -------------------------------------- tballison opened a new pull request, #1684: URL: https://github.com/apache/tika/pull/1684 <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-XXXX`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-XXXX] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! > Figure out what to do with epubs with encrypted non-core content > ---------------------------------------------------------------- > > Key: TIKA-4219 > URL: https://issues.apache.org/jira/browse/TIKA-4219 > Project: Tika > Issue Type: Task > Reporter: Tim Allison > Priority: Major > > On TIKA-4218, we noticed several epubs that were now being identified as > encrypted, which is good. We did this work on TIKA-4176. > On the other hand, we found several epubs that were now identified as > encrypted but which had content before we were doing the encryption detection. > The issue in at least one file that I reviewed is that non-core content is > encrypted -- the fonts. So, from a text+metadata extraction, we could still > get all the content and then throw an Encrypted Exception or maybe flag > something as encrypted. > I'm not sure what the best thing to do is in this case. > An example file is here: > http://corpora.tika.apache.org/base/docs/commoncrawl3/47/47WOSBEUHE6CRMVDFBOOHUD36FEQAZ6T -- This message was sent by Atlassian Jira (v8.20.10#820010)