Proposal Details
Proposal details
The cipher suite variables should be exposed so that when and if ciphers are added or modified downstream libraries and applications that depend on them can take that in to account. For example for InfluxDB we are attempting to add additional logging for TLS configurations. We support FIPS and so I would like to take in to account the ciphers being used with my log messaging. I pull out the cipher suite details from here in the go upstream:
|
// defaultCipherSuitesFIPS are the FIPS-allowed cipher suites. |
|
var defaultCipherSuitesFIPS = []uint16{ |
|
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, |
|
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, |
|
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, |
|
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, |
|
} |
It would be more preferable to be able to just call an exported variable or function directly from the language library instead of hard coding it.
Proposal Details
Proposal details
The cipher suite variables should be exposed so that when and if ciphers are added or modified downstream libraries and applications that depend on them can take that in to account. For example for InfluxDB we are attempting to add additional logging for TLS configurations. We support FIPS and so I would like to take in to account the ciphers being used with my log messaging. I pull out the cipher suite details from here in the go upstream:
go/src/crypto/tls/defaults.go
Lines 120 to 126 in ca46497
It would be more preferable to be able to just call an exported variable or function directly from the language library instead of hard coding it.