Skip to content
This repository has been archived by the owner on Sep 29, 2024. It is now read-only.

Tolerate weak certificates #97

Closed
keeshux opened this issue May 5, 2019 · 3 comments
Closed

Tolerate weak certificates #97

keeshux opened this issue May 5, 2019 · 3 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@keeshux
Copy link
Member

keeshux commented May 5, 2019

Servers using weak cryptography (e.g. PureVPN) may fail TLS handshake with error 204.

@keeshux keeshux self-assigned this May 5, 2019
@keeshux keeshux added the enhancement New feature or request label May 5, 2019
@keeshux keeshux added this to the 1.7.1 milestone May 5, 2019
@keeshux keeshux closed this as completed in 97f178c May 5, 2019
@ghost
Copy link

ghost commented May 5, 2019

Would it be possible to make this per-provider configurable? What is the OpenSSL default? It seems to depend on how OpenSSL was compiled... I'd recommend having a default of 2 or 3 and allow per-provider override...

Does SSL_CTX_set_security_level override SSL_CTX_set_options by any chance? This could potentially enable downgrade attacks?

See also https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set_security_level.html

@keeshux
Copy link
Member Author

keeshux commented May 5, 2019

WARNING at this time setting the security level higher than 1 for general internet use is likely to cause considerable interoperability issues and is not recommended.

About the override I don't really know. It seems that the level was raised with "recent versions", given that I find related pages dating 2018. Making it configurable is certainly possible.

@ghost
Copy link

ghost commented May 5, 2019

I saw the warning, but this is not "general internet use". Also, I don't know from which year this warning is as level 1 allows SHA1 and SSLv3 which should never be used any more. So level 2 is the baseline now for what is still considered secure, anything lower than 2 should be a concious choice...

The other part of my question regarding option overrides is also (very) important. Did you test for this? I can't find it in that man page, but maybe I am missing it.

Even better seems to be to always require level 2 and only list VPN providers that offer level 2 or higher, seems like a bad idea to make it easy for users to use insecure VPN providers...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant