Skip to content

Commit e340b8f

Browse files
sam-githubMylesBorins
authored andcommitted
tls: re-define max supported version as 1.2
Several secureProtocol strings allow any supported TLS version as the maximum, but our maximum supported protocol version is TLSv1.2 even if someone configures a build against an OpenSSL that supports TLSv1.3. Fixes: #24658 PR-URL: #25024 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
1 parent 2516e9c commit e340b8f

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

src/node_crypto.cc

+6
Original file line numberDiff line numberDiff line change
@@ -501,6 +501,12 @@ void SecureContext::Init(const FunctionCallbackInfo<Value>& args) {
501501
SSL_SESS_CACHE_NO_AUTO_CLEAR);
502502

503503
SSL_CTX_set_min_proto_version(sc->ctx_.get(), min_version);
504+
505+
if (max_version == 0) {
506+
// Selecting some secureProtocol methods allows the TLS version to be "any
507+
// supported", but we don't support TLSv1.3, even if OpenSSL does.
508+
max_version = TLS1_2_VERSION;
509+
}
504510
SSL_CTX_set_max_proto_version(sc->ctx_.get(), max_version);
505511
// OpenSSL 1.1.0 changed the ticket key size, but the OpenSSL 1.0.x size was
506512
// exposed in the public API. To retain compatibility, install a callback

0 commit comments

Comments
 (0)