Replies: 1 comment
-
The log already contains your answer:
This is not the OpenSSL 3.0.0 to 3.0.1 but rather a bug in 0.7.29 that would set tls-profile to insecure if not defined. And this is not about cipher suites. This is about the signing algorithm of the certificates that you are using. You can see them if do something like And yes ASUS routers are known to still generate certificates with MD5/SHA1 unfortunately. You have to either get a fix from ASUS or live with the insecure setting. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
To make issues more manageable, I would appreciate it if you fill out the following details as applicable:
General information
Description of the issue
Openvpn 0.7.29 was working for fine for me. When i upgraded to 0.7.31. the connection no longer works. I'm not sure exactly what's wrong but i suspect it to be the cipher suite that i'm using. Not sure how to set the suite though cuz my router has a limit options.
I think it is an OpenSSL problem, as 0.7.31 uses OpenSSL 3.0.1 but 0.7.29 uses OpenSSL 3.0.0. Can someone help to explain why the connection fails?
Also, when i set the tls security profile in 0.7.31 to insecure (as stated in the faq), the connection works. However, i don't see where my settings are insecure, and why the same configuration works for 0.7.29 but not for 0.7.31. I don't have to set my tls security profile to insecure in 0.7.29 though.
My cipher suite does not use md5, afaik. My openvpn client settings are at the bottom of the post.
All sensitive information have been redacted.
****** Log from 0.7.29 (aka working version) ******
Beta Was this translation helpful? Give feedback.
All reactions