Bug 27755 - Using the Subtle Crypto Interface with Streams
Open
Nobody has claimed this yet.
needs implementor interest
positive signals from web developers
proposal
- Dominant language
- HTML
- Stars
- 294
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Though the StreamsAPI is referenced in Informative Reference, the functions under window.crypto.subtle are specified with only one-shot data inputs.
Use-cases: Data may not be available at once. Data may be too huge to keep in memory.
For encrypt()/decrypt() it would make sense to have a streaming readable output if the input is a readable stream.
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
Start with the linked Bug 27755 and the window.crypto.subtle encrypt()/decrypt() entry points. Review how the Streams API is referenced and the existing one-shot input model. Done means specifying and implementing streaming behavior for cases where input is unavailable at once or too large to keep in memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100