On Tue, Feb 13, 2024 at 6:49 PM Mark Thomas <ma...@apache.org> wrote: > > On 13/02/2024 16:57, Mark Thomas wrote: > > On 13/02/2024 14:14, Rémy Maucherat wrote: > > <snip/> > > >> I tested a fresh build of trunk (3.3 dev) and it seems to work fine > >> for me on Linux. What is the error ? > > > > This isn't OpenSSL or Java EA version related. > > > > There error is: > > > > "WARNING: <path to java executable> is loading libcrypto in an unsafe way" > > > > and then the JVM exits. > > > > It is caused by this commit: > > https://github.com/apache/tomcat/commit/830771823edbb79d2884eb1c6f5122e81df4df78 > > Need to decide what to do about this: > - fix it later > - try and fix it now > - revert the change and fix it later
I need to report it to the FFM team, because from your finding it is now trying to load the wrong thing. OTOH, it did fix the library loading for the CI runs (previously libssl was not found), so it's not all on the regression side. Given that I would prefer ignoring it in this build. Rémy > > I found this GitHub issue comment > > > > https://github.com/cl-plus-ssl/cl-plus-ssl/issues/114#issuecomment-770370592 > > > > that suggests that what is happening is Tomcat is trying to load > > "/usr/lib/libcrypto.dylib" which is a stub which is intended to trigger > > the crash. > > > >>> 2. I'm seeing a couple of HTTP/2 test failures on Windows. > > > > I'm looking at these now. > > These are fixed. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
