Date: Fri, 01 Nov 2019 03:25:43 +0000 From: bugzilla-noreply@freebsd.org To: elastic@FreeBSD.org Subject: [Bug 241312] sysutils/logstash6 Cipher Error Message-ID: <bug-241312-37421-svAR9e9Iwr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241312-37421@https.bugs.freebsd.org/bugzilla/> References: <bug-241312-37421@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241312 --- Comment #9 from Greg Lewis <glewis@FreeBSD.org> --- I need to get into this deeper, but some other potential concerns: * netty-tcnative looks like it will build native libraries against libressl, boringssl, and openssl. You can't have all of those installed at once from ports because they conflict with each other (boringssl doesn't list the conflict, but it clearly has it). So there are some gymnastics that would = need to happen there to allow the full netty-tcnative build to work. * The JAR in logstash isn't the full netty-tcnative JAR, it's the one linked against boringssl based on the name (netty-tcnative-boringssl-static-2.0.12.Final.jar). That's unfortunate in = that I'm guessing boringssl is the least likely of the three for someone to have installed (given the general state of the project and port). One question I have here, without knowing the answer yet, is whether LogSta= sh is doing anything that is specific to boringssl? My guess would be no, sin= ce the tc-native code allows all three libraries to potentially be used as the native component. If that is the case, then it might be possible to build a native library for FreeBSD using whatever SSL lib is set as the default or maybe ignore ports altogether and build it against the system installed version. The dependen= cy on apr might mean we have to use the version in ports though, I haven't che= cked into that. Were that the case, it might make more sense to do it within the LogStash port and just build that library and add it into the JAR rather th= an attempt a general netty-tcnative port since that is going to have problems. Is someone either able to test or willing to share configuration files and testing steps if I were to try and put something like that together? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241312-37421-svAR9e9Iwr>