-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
tls: remove tls_legacy, createSecurePair #5924
Conversation
I don't think this can be removed without some sort of deprecation cycle. |
This is a semver-major change. Remove SecurePair, createSecure pair from API. Remove internal Connection class and SecurePair tests.
|
76c28bc
to
14b8e5a
Compare
A deprecation cycle would definitely be required first. |
@jasnell what exactly is missing? I believe |
@indutny I think it needs to be deprecated at the code level via |
@mscdex perhaps there is a bug in docs, but it is deprecated: https://nodejs.org/api/tls.html#tls_class_cryptostream |
@indutny There is no connection between |
@mscdex yeah, looks like we will need to deprecate it first then. 😢 @jhamhader sorry, but this PR will have to wait a release cycle |
Will submit a deprecation PR and resume effort on SNI callback issue. |
7da4fd4
to
c7066fb
Compare
c133999
to
83c7a88
Compare
Closing in favor of #11349 |
Pull Request check-list
Please make sure to review and check all of these items:
make -j8 test
(UNIX) orvcbuild test nosign
(Windows) pass withthis change (including linting)?
test (or a benchmark) included?
existing APIs, or introduces new ones)?
NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Affected core subsystem(s)
Please provide affected core subsystem(s) (like buffer, cluster, crypto, etc)
Description of change
Please provide a description of the change here.
This is a semver-major change.
Remove SecurePair, createSecure pair from API.
Remove internal Connection class and SecurePair tests.