-
Story
-
Resolution: Obsolete
-
Undefined
-
None
-
None
As part of the initial 2.2 build we had to disable the envoy.tls.key_providers.cryptomb because it was not ported to OpenSSL from BoringSSL.
We need to make the changes and re-enable it before 2.2.0. If we decide this is not something we want for 2.2 we can close this as "Won't Fix".
This doesn't require any work from QE. There are upstream tests that cover this feature/extension.
UPDATE: We are not going to ship this in 2.2.0. Let's keep this issue around for future work.