-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
crypto.createDiffieHellman
results in an abort
#38302
Labels
Comments
Can confirm on master I'm working on this |
EladKeyshawn
pushed a commit
to EladKeyshawn/node
that referenced
this issue
Apr 20, 2021
EladKeyshawn
pushed a commit
to EladKeyshawn/node
that referenced
this issue
Apr 20, 2021
EladKeyshawn
pushed a commit
to EladKeyshawn/node
that referenced
this issue
Apr 20, 2021
targos
pushed a commit
that referenced
this issue
Apr 29, 2021
PR-URL: #38311 Fixes: #38302 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What steps will reproduce the bug?
Setup a node instance,
and run the following javascript code.
Then the node instance occurs an abort.
How often does it reproduce? Is there a required condition?
This abort can always be triggered following the steps above.
What is the expected behavior?
If any error occurs, an exception or other similar error-reporting stuff should be thrown. There is no reason to abort the whole node process.
What do you see instead?
Additional information
The text was updated successfully, but these errors were encountered: