Sebastian,
Thank You for You help. I added "-cipher DEFAULT:@SECLEVEL=0" and this
resolved the case.
Pozdrawiam serdecznie
Maciej Bogucki
On 11.03.2024 18:23, Sebastian Andrzej Siewior wrote:
On 2024-03-11 13:29:10 [+0100], Maciej Bogucki wrote:
Hi,
Hi,
When I use stiati compiled
On 2024-03-11 13:29:10 [+0100], Maciej Bogucki wrote:
> Hi,
Hi,
> When I use stiati compiled openssl form different system I can have the
> connection
>
> root@nsd-sdproxy1:~# /tmp/openssl version
> OpenSSL 1.0.1t 3 May 2016
that is stone age.
> root@nsd-sdproxy1:~# /tmp/openssl s_client
Hi,
Thank You for the reply.
Port is open
root@nsd-sdproxy1:~# telnet 192.168.92.95 636
Trying 192.168.92.95...
Connected to 192.168.92.95.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
root@nsd-sdproxy1:~#
When I use stiati compiled openssl form different system I can have the
Hi,
I have just added CA to ca-certificates and updated them using
/usr/sbin/update-ca-certificates
root@nsd-sdproxy1:~# ls -l /usr/local/share/ca-certificates/
total 4
-rw-r--r-- 1 root root 1238 Mar 11 13:01 dc1_CA.crt
root@nsd-sdproxy1:~#
I still can't connect to server
On 2024-03-04 11:16:14 [+0100], Maciej Bogucki wrote:
> When I invoke `/usr/bin/openssl s_client -connect 192.168.92.95:636`
So you get no reply? That is odd. There has to be reply. A "Connected"
line is something I would have expected. If there is nothing then I
would assume that the port is
Hi,
It's unclear to me what you're reporting as error. The connection seems to be
working. The verification of the certificate seems to fail. It seems you have
your own CA, but the CA is not trusted because it's not in the certificate
store.
Kurt
Package: openssl
Version: 3.0.11-1~deb12u2
When I invoke `/usr/bin/openssl s_client -connect 192.168.92.95:636`
root@nsd-sdproxy1:~# cat /etc/debian_version
12.5
root@nsd-sdproxy1:~#
root@nsd-sdproxy1:~# uname -a
Linux nsd-sdproxy1 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1
7 matches
Mail list logo
