-
Notifications
You must be signed in to change notification settings - Fork 101
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
Phase out weak ciphers? #101
Comments
/cc @thaJeztah @AkihiroSuda @neersighted Related to moby/moby#45121 |
PTAL @corhere as well; I have no strong opinions -- if no others appear, maybe we discuss this on Thursday? |
Yeah, we still need to dig into the TLS1.3 issue as well; updating moby to the latest code in this repo breaks things (see moby/moby#41084 and the original PR linked) |
Seems strange that we even have tlsconfig in this repo. |
Yeah, ISTR the original reason was to have a canonical place where these were defined (as at the time it was not always trivial to decide on the ciphers, and to make sure all repositories followed the same) |
We have this comment:
go-connections/tlsconfig/config.go
Line 43 in 58542c7
Perhaps it is time to go ahead and make good on that comment?
The text was updated successfully, but these errors were encountered: