Hi Martijn,
Doh! I was looking at the netty-tcnative-openssl-static module, not the one
pulled in by Flink netty-tcnative-boringssl-static, which is of course
building BoringSSL not OpenSSL. So the legal issue stands.
Maybe there's a possibility to offer netty-tcnative-openssl-static as an
option
Hi Rob,
While Netty TCNative has upgraded to Openssl 3, there are still references
to BoringSSL [1]. Do you know if TCNative still uses BoringSSL as well in
this version?
Best regards,
Martijn
[1]
https://github.com/netty/netty-tcnative/blob/netty-tcnative-parent-2.0.62.Final/license/LICENSE.bo
Hi,
I see in flink-shaded main we depend
on 2.0.62.Final and we
currently avoid building/distributing flink-shaded-netty-tcnative-static
due to legal issues
> This module is excluded by default since it is not compliant with the
apache license. https://issues.apache.org/jira/browse/LEGAL-393
net
