Bug 247236

Summary: www/envoy is marked as broken: does not build with DEFAULT_VERSIONS+=ssl=base: requires BoringSSL
Product: Ports & Packages Reporter: uros
Component: Individual Port(s)Assignee: Alexey Dokuchaev <danfe>
Status: New ---    
Severity: Affects Some People CC: danfe
Priority: --- Flags: linimon: maintainer-feedback? (danfe)
Version: Latest   
Hardware: Any   
OS: Any   

Description uros 2020-06-13 13:42:19 UTC
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.
Comment 1 Alexey Dokuchaev freebsd_committer 2020-06-16 15:20:10 UTC
(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.

*) https://github.com/envoyproxy/envoy-openssl
Comment 2 uros 2021-01-24 19:42:45 UTC
@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
Comment 3 uros 2021-03-30 18:19:55 UTC
Any reason why we can't use https://svnweb.freebsd.org/ports/head/security/boringssl/