-
Notifications
You must be signed in to change notification settings - Fork 30.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Non-streaming encryption api #941
Comments
+1 |
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. |
I don't think think we need to have such complex key management objects and On Wed, Feb 25, 2015 at 12:32 AM Domenic Denicola [email protected]
|
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. |
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? |
ccm mode doesn't work currently due to the streaming nature |
Is this basically in a "waiting for someone to implement it" state? @nodejs/crypto |
That, and the API needs to be hashed out. |
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. |
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.
The text was updated successfully, but these errors were encountered: