Verifying huge signed files (with attached signature) could immediately oom.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Admittedly, again, this is not new. But do you think we can feed this as a stream into pysequoia?
Originally posted by @mdellweg in #7433
Contributor guide
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
No files, tests, or entry points are named. Start by tracing the signed-file verification path and its pysequoia integration, then determine whether verification can consume a stream. Done means huge signed files no longer immediately cause out-of-memory failures while signature verification remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100