Tobias Nießen 1640aeb680 crypto: remove obsolete SSL_OP_* constants ... 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: https://github.com/nodejs/node/pull/46954 Refs: https://github.com/nodejs/node/pull/47066 PR-URL: https://github.com/nodejs/node/pull/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>		2023-03-21 10:47:49 +00:00
..
internalBinding	crypto: remove obsolete SSL_OP_* constants	2023-03-21 10:47:49 +00:00
globals.d.ts	typings: improve internal bindings typings	2021-10-28 07:52:29 +00:00
primordials.d.ts	typings: improve primordials typings	2023-03-08 10:47:26 +00:00