Bug#1065424: [Pkg-openssl-devel] Bug#1065424: Can't connect to Active Directory with openssl

2024-03-11 Thread Maciej Bogucki
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

Bug#1065424: [Pkg-openssl-devel] Bug#1065424: Can't connect to Active Directory with openssl

2024-03-11 Thread Maciej Bogucki
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

Bug#1065424: [Pkg-openssl-devel] Bug#1065424: Can't connect to Active Directory with openssl

2024-03-04 Thread Sebastian Andrzej Siewior
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

Bug#1065424: [Pkg-openssl-devel] Bug#1065424: Can't connect to Active Directory with openssl

2024-03-04 Thread Kurt Roeckx
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