Use golang's supported CipherSuites() and InsecureCipherSuites() to populate our mapping of cipher suite names to ID. However we have supported legacy cipher suite names, as well as openssl cipher suite names in the past, so those remain explicitly added.
Newer (TLS 1.3) cipher suites in openssl seem to use the same suite names as RFC format, so maybe we don't need to worry about future translations between OpenSSL + RFC naming formats. If that changes, we're no worse off than we are now, needing to manually add the cipher suites.
[x] I have viewed signed and have submitted the Contributor License Agreement
[x] I have made this pull request to the main branch
Use golang's supported CipherSuites() and InsecureCipherSuites() to populate our mapping of cipher suite names to ID. However we have supported legacy cipher suite names, as well as openssl cipher suite names in the past, so those remain explicitly added.
Newer (TLS 1.3) cipher suites in openssl seem to use the same suite names as RFC format, so maybe we don't need to worry about future translations between OpenSSL + RFC naming formats. If that changes, we're no worse off than we are now, needing to manually add the cipher suites.
[x] I have viewed signed and have submitted the Contributor License Agreement
[x] I have made this pull request to the
mainbranch[x] I have run all the unit tests.
[ ] (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests
[ ] (Optional) I have run CF Acceptance Tests