Skip to content
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

allow TLS 1.3 ciphersuites after 3DES suites and Go 1.13.1 #257

Merged
merged 3 commits into from
Sep 27, 2019

Conversation

jmhodges
Copy link
Owner

@jmhodges jmhodges commented Sep 27, 2019

The ciphersuites for TLS 1.3 are fine to come after any 3DES suites because they
are a completely disjoint set from any previous versions TLS 1.2 version. Older
versions of TLS don't support them, and TLS 1.3 doesn't support the older
ciphersuites.

This came up because Go 1.13 and later are sending them by default now.

We also do an upgrade to Go 1.13.1 because I wasn't able to get a local development environment that matched what was currently in howsmyssl's CI. Welp.

The ciphersuites for TLS 1.3 are fine to come after any 3DES suites because they
are a completely disjoint set from any previous versions TLS 1.2 version. Older
versions of TLS don't support them, and TLS 1.3 doesn't support the older
ciphersuites.

This came up because Go 1.13 and later are sending them by default now.
@jmhodges jmhodges changed the title allow TLS 1.3 ciphersuites after 3DES suites allow TLS 1.3 ciphersuites after 3DES suites and Go 1.13.1 Sep 27, 2019
@jmhodges jmhodges merged commit ac0fbf2 into master Sep 27, 2019
@jmhodges jmhodges deleted the handle_tls13 branch September 27, 2019 23:43
@jmhodges jmhodges mentioned this pull request Sep 27, 2019
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