viewtopic.php?f=7&t=30633&p=93136#p93136
I have an ARM v7 with OpenVPN server version
Code: Select all
OpenVPN 2.4.7 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 28 2021
library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10
Originally developed by James Yonan
I have a NON-WORKING Windows 10 client with OpenVPN version 2.5.0 to 2.5.3 (I test them all).
NON-WORKING means: viewtopic.php?f=22&t=33023&p=102165#p102165
When I insert the .conf file with inline certificates from WORKING client to NON-WORKING client, NON-WORKING client still does not work.
When I replace ALL the .EXE and DLL files to NON-WORKING client from them to WORKING client, NON-WORKING client WORKS!
So, something happen from version 2.5.0 beta 1 to version 2.5.0.
Also the 2.5.0 beta 1 becomes valuable because it is not available for download.
UPDATE:
Downgrading libcrypto-1_1-x64.dll from 1.1.1.8 (2.5.0) to 1.1.1.7 (2.5.0 beta1) fixes the problem.
So the question is what this means?
Code: Select all
Changes between 1.1.1g and 1.1.1h [22 Sep 2020]
Certificates with explicit curve parameters are now disallowed in verification chains if the X509_V_FLAG_X509_STRICT flag is used.