Change Details

Currently acme-chief offers some features that are being ignored by its clients: * dual-cert set-up * OCSP stapling support Currently (almost) every acme-chief client should be able to serve a dual-cert setup but all of them are using RSA-2048 certificates. (Take into account that our [[ https://grafana.wikimedia.org/d/000000458/tls-ciphersuite-explorer?panelId=5&fullscreen&orgId=1 | TLS traffic is mostly using ECDSA certificates ]]). Regarding OCSP stapling, at least nginx based acme-chief clients should be able to use it.

Currently acme-chief offers some features that are being ignored by its clients: [x] dual-cert set-up: all acme-chief clients that support dual-cert stack are currently using ECDSA+RSA certificates [] OCSP stapling support Currently (almost) every acme-chief client should be able to serve a dual-cert setup but all of them are using RSA-2048 certificates. (Take into account that our [[ https://grafana.wikimedia.org/d/000000458/tls-ciphersuite-explorer?panelId=5&fullscreen&orgId=1 | TLS traffic is mostly using ECDSA certificates ]]). Regarding OCSP stapling, at least nginx based acme-chief clients should be able to use it.

Currently acme-chief offers some features that are being ignored by its clients: *[x] dual-cert set-up-up: all acme-chief clients that support dual-cert stack are currently using ECDSA+RSA certificates *[] OCSP stapling support Currently (almost) every acme-chief client should be able to serve a dual-cert setup but all of them are using RSA-2048 certificates. (Take into account that our [[ https://grafana.wikimedia.org/d/000000458/tls-ciphersuite-explorer?panelId=5&fullscreen&orgId=1 | TLS traffic is mostly using ECDSA certificates ]]). Regarding OCSP stapling, at least nginx based acme-chief clients should be able to use it.