Hello Martin and John,
Any update on this?
Regards with Thanks,
Fang
On Thu, 4 Jun 2020, 09:48 FANG YAP, wrote:
> Hi Martin,
>
> Thank you for your email.
>
> In my application's web.xml, there is already a default
> error-code that defines 404 (../error_404.jsp), 403 (../error_403.jsp),
Hi Michael,
Thank you I will review paths during config.
Warm regards,
Norbert Elbanbuena
Check out our new Website
-Original Message-
From: Michael Osipov
Sent: Sunday, June 7, 2020 2:50 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 9.0.27 loads incorrect openssl version
Am 2020-06-07 um 21:31 schrieb Norbert Elbanbuena:
Hi Michael,
Interesting I find multiple files.
You have managed to mess up your system. The loader hierarchy looks wrong.
# ldd -v /usr/lib/libtcnative-1.so
I assume that this is provided by your package manager. If so
Hi Michael,
Interesting I find multiple files.
# ldd -v /usr/lib/libtcnative-1.so
linux-vdso.so.1 => (0x7ffd767f9000)
libssl.so.1.1 => /usr/local/ssl/lib/libssl.so.1.1 (0x7f33f497b000)
libcrypto.so.1.1 => /usr/local/ssl/lib/libcrypto.so.1.1
(0x7f33f4491000)
Am 2020-06-07 um 20:16 schrieb Norbert Elbanbuena:
Hi,
I removed the previous version of OpenSSL 1.0.2k-fips from yum. Then I
installed OpenSSL 1.1.1g from source and made a clean install of tomcat-native
1.2.24 pointing to the correct OpenSSL path.
When I start Tomcat, it still shows OpenSSL
Hi,
I removed the previous version of OpenSSL 1.0.2k-fips from yum. Then I
installed OpenSSL 1.1.1g from source and made a clean install of tomcat-native
1.2.24 pointing to the correct OpenSSL path.
When I start Tomcat, it still shows OpenSSL 1.0.2k-fips being loaded on startup.
07-Jun-2020
