-
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
src: move more crypto_dh.cc code to ncrypto #54459
Conversation
Review requested:
|
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fear making it semver-major will make backporting all of the ncrypto PR very hard/impossible.
An option is to mark all of them to not be backported on v22 (unless this ship has already sailed).
Looks like part of the early ncrypto stuff is already in 22... sigh. Ok, let me go back and figure out how to make this non-semver-major. |
Ok, backed the error code changes out. Not super ideal but makes it semver-patch instead of major. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@jasnell can you update the PR description? |
This comment was marked as outdated.
This comment was marked as outdated.
Update deps/ncrypto/ncrypto.cc
Update deps/ncrypto/ncrypto.cc PR-URL: #54459 Reviewed-By: Yagiz Nizipli <[email protected]>
Landed in 6bf7b6e |
Update deps/ncrypto/ncrypto.cc PR-URL: #54459 Reviewed-By: Yagiz Nizipli <[email protected]>
Update deps/ncrypto/ncrypto.cc PR-URL: #54459 Reviewed-By: Yagiz Nizipli <[email protected]>
Moving more bits and pieces to ncrypto.
Unfortunately this is semver-major because it changes error codes in a couple of places. The change is worth it as it simplifies a few things and eliminates a special case error code that is only used in this one spot. This could be made semver-patch or semver-minor with a bit more work but it makes the API a bit more awkward. I'd rather not but if folks prefer it we can.No longer semver-majorWhile I'm at it, this makes a number of other cleanups along the way.