trailofbits / trailofbits/polyfile
Low, low priority: Consider alternate handling for encrypted Zip streams
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 390
- Forks
- 31
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 72
Description
In this example file: https://github.com/apache/tika/blob/master/tika-parsers/src/test/resources/test-documents/testZipEncrypted.zip, one of the streams is encrypted, and the other isn't.
It might be useful to report an encrypted stream in the output json and then process the unencrypted file type rather than throwing an exception on the file and not processing it at all.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the linked test-documents/testZipEncrypted.zip example as the reproduction input, then trace how polyfile handles mixed encrypted and unencrypted streams and where it emits output JSON or raises the exception. Done means the encrypted stream is represented in the output and the unencrypted file type is still processed without aborting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100