Tim Walsh
Tim Walsh
Not at this time, once we have stabilized some library code we can look at providing an image.
The integration option with Istio is still pending. The Maistra version of Envoy is a refactored version to work with OpenSSL 1.1.1 and is a component of Service Mesh. The...
Tasks: 1. Review upstream envoy for all calls to boring ssl 2. Review openssl 3 release notes for compatability with 1.1.1 3. Implement wrapper functions / calls to OpenSSL. 4....
See notes on [RAND_bytes()](https://github.com/envoyproxy/envoy-openssl/pull/54)
Yes we are using OpenSSL 3.0 On Wed, Dec 13, 2023 at 8:28 AM Elvain ***@***.***> wrote: > So open ssl 3,0 already supported right now? > > — >...
We are using OpenSSL 3 as a shared library and using OpenSSL 3 fips provider support.
We have the older version of envoy-openssl that is out of date, essentially though it is a bazel build similar to the envoy repository and is built from the envoy-openssl...
The Maistra version is the EnvoyProxy version modified to use OpenSSL rather than BoringSSL. The original intent was to make Maistra the basis for a more general envoy-openssl version of...
Envoy relies on BoringSSL to support QUIC/HTTP3 OpenSSL requires an [Akamai](https://www.akamai.com/blog/performance/http3-and-quic-past-present-and-future) patch to support. This currently breaks the integrity for FIPS. 1. Identify OpenSSL 3.x support plans for QUIC 2....
This problem is related to BoringSSL not building on S390. BoringSSL is build for compatibility testing. This is a known problem and is being reviewed.