Repository navigation
Proposal: Non-streaming encryption api #941
Description
The steaming format is a poor fit for authenticated ciphers so one idea would be to make a new non streaming api for encryption (maybe just authenticated encryption?) to avoid situations where we are decrypting data we have not authenticated.
This would also allow us to impliment ccw mode which I seem to recall having issues related to needing to know the message length ahead of time.
I can try throwing together a pull if people like this idea.
Activity
mikeal commentedon Feb 24, 2015
+1
domenic commentedon Feb 25, 2015
Might be a different issue (maybe spin it off into NG if so) but I'd be curious to see to what extent your thinking aligns with web crypto's APIs.
calvinmetcalf commentedon Feb 25, 2015
I don't think think we need to have such complex key management objects and
I'd probably want the parameters to be slightly more consistent (all in an
object or none in an object), Plus we'd need a synchronous version not just
an async version. I've found, in general, that the subtle crypto api is
way too complex.
On Wed, Feb 25, 2015 at 12:32 AM Domenic Denicola notifications@github.com
wrote:
calvinmetcalf commentedon Feb 26, 2015
wait nope, probably not able to do this myself, don't know enough c++ and got stuck trying to figure out where ctx_ was defined.
seishun commentedon Oct 16, 2015
Most of crypto is synchronous. You can just easily write non-streaming wrappers in JS-land. Or are you talking about some specific crypto function where this wouldn't work?
calvinmetcalf commentedon Jan 6, 2016
ccm mode doesn't work currently due to the streaming nature
Trott commentedon Jun 25, 2016
Is this basically in a "waiting for someone to implement it" state?
@nodejs/crypto
bnoordhuis commentedon Jun 26, 2016
That, and the API needs to be hashed out.
bnoordhuis commentedon Sep 14, 2017
I'll go ahead and close out this issue. It's been open for 2.5 years with no movement whatsoever; the last comment was my own and that was over a year ago.