We got to the root cause of my failures - TLSv1.2 uses larger hashes, which the windows cryptoapi interface doesn't support.

From your log, suspect you may have a similar issue with a different certificate loader. Are you using pkcs11 to provide the client cert? An external keyring?

Your failure is where a client certificate is being prepared to be sent to the server for authentication. It's producing a signature that's the wrong size (meaning, it's the wrong type.)

The failing client config file would help to validate this theory. Don't need anything secret.

(Still not a developer, but I have become (too) familiar with this code over the last several daze. So I thought I should try to help.)

--
Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed.


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to