Skip to content

Always allow both TLS 1.2 and 1.3 in the proxy#2978

Open
gbrodman wants to merge 1 commit intogoogle:masterfrom
gbrodman:proxyTls
Open

Always allow both TLS 1.2 and 1.3 in the proxy#2978
gbrodman wants to merge 1 commit intogoogle:masterfrom
gbrodman:proxyTls

Conversation

@gbrodman
Copy link
Collaborator

@gbrodman gbrodman commented Mar 6, 2026

The JDK version of SSL has long supported TLS v1.3 (since version 11) so fortunately we can use TLS v1.3 regardless if which implementation of SSL we're using.

We prefer OpenSSL in general so I'm not entirely sure why we were using the JDK version of SSL on the proxy before, but this should work and be a good idea regardless.

Tested on alpha by running

$ openssl s_client -connect epp.registryalpha.foo:700 -tls1_3 -ciphersuites "TLS_AES_128_GCM_SHA256"

Previously we'd get a failure, now it returns the proper cert data.


This change is Reviewable

The JDK version of SSL has long supported TLS v1.3 (since version 11) so
fortunately we can use TLS v1.3 regardless if which implementation of
SSL we're using.

We prefer OpenSSL in general so I'm not entirely sure why we were using
the JDK version of SSL on the proxy before, but this should work and be
a good idea regardless.

Tested on alpha by running

```
$ openssl s_client -connect epp.registryalpha.foo:700 -tls1_3 -ciphersuites "TLS_AES_128_GCM_SHA256"
```

Previously we'd get a failure, now it returns the proper cert data.
@gbrodman gbrodman changed the title Always allow both TLS 1.2 and 1.3 Always allow both TLS 1.2 and 1.3 in the proxy Mar 6, 2026
@gbrodman gbrodman requested a review from weiminyu March 7, 2026 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant