-
Notifications
You must be signed in to change notification settings - Fork 30k
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
doc: remove useless SSL_OP_* options #46954
Merged
nodejs-github-bot
merged 1 commit into
nodejs:main
from
tniessen:doc-crypto-remove-useless-ossl-ctx-options
Mar 6, 2023
Merged
doc: remove useless SSL_OP_* options #46954
nodejs-github-bot
merged 1 commit into
nodejs:main
from
tniessen:doc-crypto-remove-useless-ossl-ctx-options
Mar 6, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These 14 options do not have any effect in any supported version of OpenSSL.
tniessen
added a commit
to tniessen/node
that referenced
this pull request
Mar 4, 2023
This option does not have any effect in any supported OpenSSL version. Refs: nodejs#46954
bnoordhuis
approved these changes
Mar 5, 2023
panva
approved these changes
Mar 5, 2023
panva
added
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
commit-queue
Add this label to land a pull request using GitHub Actions.
labels
Mar 5, 2023
cjihrig
approved these changes
Mar 5, 2023
lpinca
approved these changes
Mar 5, 2023
aymen94
approved these changes
Mar 6, 2023
nodejs-github-bot
removed
the
commit-queue
Add this label to land a pull request using GitHub Actions.
label
Mar 6, 2023
Landed in db81af6 |
tniessen
added a commit
to tniessen/openssl
that referenced
this pull request
Mar 6, 2023
SSL_OP_NETSCAPE_CA_DN_BUG became obsolete in 3c33c6f and support for SSL_OP_NETSCAPE_DEMO_CIPHER_CHANGE_BUG was removed by 7a4dadc. The definitions are still listed under "OBSOLETE OPTIONS retained for compatibility" in ssl.h.in, so this commit adds them to the list of obsolete options in doc/man3. Refs: nodejs/node#46954
1 task
targos
pushed a commit
that referenced
this pull request
Mar 13, 2023
These 14 options do not have any effect in any supported version of OpenSSL. PR-URL: #46954 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
tniessen
added a commit
to tniessen/node
that referenced
this pull request
Mar 13, 2023
I missed these two in db81af6 because I went by OpenSSL's list of obsolete flags, which turned out to be incomplete. See openssl/openssl#20443. Refs: nodejs#46954 Refs: openssl/openssl#20443
nodejs-github-bot
pushed a commit
that referenced
this pull request
Mar 13, 2023
I missed these two in db81af6 because I went by OpenSSL's list of obsolete flags, which turned out to be incomplete. See openssl/openssl#20443. Refs: #46954 Refs: openssl/openssl#20443 PR-URL: #47066 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
tniessen
added a commit
to tniessen/node
that referenced
this pull request
Mar 13, 2023
None of these constants have any effect in recent OpenSSL versions, not even in Node.js release lines that still use OpenSSL 1.1.1. It is likely rare that these options are still used (intentionally), and removing them is unlikely to break any existing applications. These constants can only be passed to the secureOptions option of tls.createSecureContext() and related APIs, and a value of undefined will be ignored. Similarly, if a bitwise combination of multiple options is used, undefined constants will not change the behavior because (a | undefined | b) === a | b for (small non-negative) integers a and b. Refs: nodejs#46954 Refs: nodejs#47066
tniessen
added a commit
to tniessen/node
that referenced
this pull request
Mar 13, 2023
None of these constants have any effect in recent OpenSSL versions, not even in Node.js release lines that still use OpenSSL 1.1.1. It is likely rare that these options are still used (intentionally), and removing them is unlikely to break any existing applications. These constants can only be passed to the secureOptions option of tls.createSecureContext() and related APIs, and a value of undefined will be ignored. Similarly, if a bitwise combination of multiple options is used, undefined constants will not change the behavior because (a | undefined | b) === (a | b) for (small) integers a and b. Refs: nodejs#46954 Refs: nodejs#47066
targos
pushed a commit
that referenced
this pull request
Mar 14, 2023
These 14 options do not have any effect in any supported version of OpenSSL. PR-URL: #46954 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
targos
pushed a commit
that referenced
this pull request
Mar 14, 2023
I missed these two in db81af6 because I went by OpenSSL's list of obsolete flags, which turned out to be incomplete. See openssl/openssl#20443. Refs: #46954 Refs: openssl/openssl#20443 PR-URL: #47066 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
openssl-machine
pushed a commit
to openssl/openssl
that referenced
this pull request
Mar 14, 2023
SSL_OP_NETSCAPE_CA_DN_BUG became obsolete in 3c33c6f and support for SSL_OP_NETSCAPE_DEMO_CIPHER_CHANGE_BUG was removed by 7a4dadc. The definitions are still listed under "OBSOLETE OPTIONS retained for compatibility" in ssl.h.in, so this commit adds them to the list of obsolete options in doc/man3. Refs: nodejs/node#46954 Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #20443)
openssl-machine
pushed a commit
to openssl/openssl
that referenced
this pull request
Mar 14, 2023
SSL_OP_NETSCAPE_CA_DN_BUG became obsolete in 3c33c6f and support for SSL_OP_NETSCAPE_DEMO_CIPHER_CHANGE_BUG was removed by 7a4dadc. The definitions are still listed under "OBSOLETE OPTIONS retained for compatibility" in ssl.h.in, so this commit adds them to the list of obsolete options in doc/man3. Refs: nodejs/node#46954 Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #20443) (cherry picked from commit fe52208)
openssl-machine
pushed a commit
to openssl/openssl
that referenced
this pull request
Mar 14, 2023
SSL_OP_NETSCAPE_CA_DN_BUG became obsolete in 3c33c6f and support for SSL_OP_NETSCAPE_DEMO_CIPHER_CHANGE_BUG was removed by 7a4dadc. The definitions are still listed under "OBSOLETE OPTIONS retained for compatibility" in ssl.h.in, so this commit adds them to the list of obsolete options in doc/man3. Refs: nodejs/node#46954 Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #20443) (cherry picked from commit fe52208)
nodejs-github-bot
pushed a commit
that referenced
this pull request
Mar 21, 2023
None of these constants have any effect in recent OpenSSL versions, not even in Node.js release lines that still use OpenSSL 1.1.1. It is likely rare that these options are still used (intentionally), and removing them is unlikely to break any existing applications. These constants can only be passed to the secureOptions option of tls.createSecureContext() and related APIs, and a value of undefined will be ignored. Similarly, if a bitwise combination of multiple options is used, undefined constants will not change the behavior because (a | undefined | b) === (a | b) for (small) integers a and b. Refs: #46954 Refs: #47066 PR-URL: #47073 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
danielleadams
pushed a commit
that referenced
this pull request
Apr 11, 2023
These 14 options do not have any effect in any supported version of OpenSSL. PR-URL: #46954 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
danielleadams
pushed a commit
that referenced
this pull request
Apr 11, 2023
I missed these two in db81af6 because I went by OpenSSL's list of obsolete flags, which turned out to be incomplete. See openssl/openssl#20443. Refs: #46954 Refs: openssl/openssl#20443 PR-URL: #47066 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
crypto
Issues and PRs related to the crypto subsystem.
doc
Issues and PRs related to the documentations.
openssl
Issues and PRs related to the OpenSSL dependency.
tls
Issues and PRs related to the tls subsystem.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These 14 options do not have any effect in any supported version of OpenSSL.