This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27755 - Using the Subtle Crypto Interface with Streams
Summary: Using the Subtle Crypto Interface with Streams
Status: RESOLVED MOVED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-05 20:47 UTC by astro
Modified: 2016-05-24 00:22 UTC (History)
6 users (show)

See Also:

Attachments

Description astro 2015-01-05 20:47:38 UTC 
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.
Comment 1 Gil Cottle 2015-12-18 06:19:48 UTC 
It would make sense for other APIs as well like digest/sign/verify.

I would love to be able to use a built-in browser API like this for validating large files client-side prior to upload to reduce failure rates of similar validations server-side.
Comment 2 jimsch 2016-03-07 23:25:15 UTC 
This has long been a desired goal, however I do not believe that there is any current effort to do this.  Propose the this be resolved as LATER.  This would allow for a version 2 spec to pick the issue up.
Comment 3 Mark Watson 2016-05-24 00:22:24 UTC 
Moved to https://github.com/w3c/webcrypto/issues/73