-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openconnect: T4982: Support defining minimum TLS version in openconnect VPN #3371
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Embezzle,
thank you for the contribution. I have some minor comments.
tls-version-min
is already defined for OpenVPN interfaces at https://github.com/vyos/vyos-1x/blob/current/interface-definitions/interfaces_openvpn.xml.in#L742 - please create a new file interface-definitions/include/tls-version-min.xml.i which can then be included by both OpenVPN and OpenConnect. This saves redundant lines and makes future maintenance easier.
In addition you define that the default TLS version will be 1.2 - this breaks backward compatibility as the current default TLS version is 1.0. You will either need to downgrade the default to 1.0 or add a migration script which explicitly defined tls-version-min to be set at 1.0 if it‘s not defined in the old configurations. As VyOS 1.4.0-epa3 is yet not released we can add this change to lift the default TLS version.
Thank you for the feedback @c-po, I have amended the PR with your requested changes. The OpenVPN interface implementation of tls-version-min did not previously have a I do not think this requires a migration script for OpenVPN, as the default minimum version supported if not explicitly configured by VyOS, as was the case before this PR, is also TLSv1.2. https://openvpn.net/community-resources/reference-manual-for-openvpn-2-6 (see section for: --tls-version-min) |
Hi @Embezzle, no need for any changes on OpenVPN code. Please remove this again as it should happen in a different PR if needed. Our OpenVPN will only have:
Whereas OpenConnect will have:
Meaning that one can overload the default of a previous XML node definition |
Hi @c-po, I did not realise you could append tags to includes in the XML definitions like shown, that makes much more sense! |
@Mergifyio backport sagitta |
✅ Backports have been created
|
Change Summary
Allow configuration of minimum acceptable TLS version for openconnect VPN.
Default is set at TLSv1.2 to ensure out-of-box/unconfigured option is not insecure.
Types of changes
Related Task(s)
https://vyos.dev/T4982
Related PR(s)
Component(s) name
vpn -> openconnect
Proposed changes
How to test
Smoketest result
Checklist: