Hi Gustaf,
It just occurred to me that my comment about OpenSSL not being automatically
configured by Naviserver was inappropriate. I was certainly not complaining and
I completely understand that things change. My apologies. What that remark
suggested was not my intention.
Thorpe
> On Nov 8,
Hi Gustaf,
Thank you for your followup.
I have reconfigured and recompiled naviserver. I do not think I have any issues
there. I have been able to update naviserver without any problems.
I installed openssl 3..0.7 again. The test showed a couple of errors. Very
likely an issue.
I am using Cen
From your original mail, i got the impression that you hand no "issues"
with NaviServer either, but you are wondering, why OpenSSL 3.* is not
"picked up automatically" and still linked against OpenSSL 1.*. Since
there are many differences between OpenSSL 1.* and 3.* [1], many
distributors do n
Hi Gustaf,
Thank you for your response and the information.
I did not have any issues with previous OpenSSL updates, although I had not
installed 3.x versions.
Best regards.
Thorpe
Thorpe Mayes
(512) 394-8766
> On 6 Nov 2022, at 11:34, Gustaf Neumann wrote:
>
>
> Dear Thorpe,
>
> it
Dear Thorpe,
it looks like you have now two versions of openssl installed on your
system, since the output "1.0.2k-fips" comes straight from the library.
So, if you see this string, the library is still there.
One can check the version used during linkage via
ldd /usr/local/ns/bin/nsd
W
Hi,
I updated OpenSSL on my server to version 3.0.7.
Prior to updating, openssl version -a showed:
OpenSSL 1.0.2k-fips 26 Jan 2017
built on: reproducible build, date unspecified
platform: linux-x86_64
options: bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int)
blowfish(idx)
compi
