envoy is broken and can't use it. There is also new version 1.14.4 outside. I guess the problem is there is no BoringSSL as ssl option. I tried to fix this myself but without success right now.
I would like to use envoy with Consul to provide connection between services.
(In reply to uros from comment #0)
> I guess the problem is there is no BoringSSL
That is correct. There is 3rd-part work* available for building Envoy purely with OpenSSL, and ultimately I'd want to divorce the port from BoringSSL, but I haven't looked in it closely yet.
@alexey can you please check https://github.com/envoyproxy/envoy-openssl/issues/1 where I asked about openssl support and I don't have anough knowledge to give concrete answer
Any reason why we can't use https://svnweb.freebsd.org/ports/head/security/boringssl/