This patch should not be applied as-is; as Chris mentions, the correct thing to do is to modify the settings in the VPN connection.
A valid workaround for n-m-openvpn would require also modifying either the value entered in the dialog to strip out part of the value (anything up and including "CN=") and keeping 'name' as the piece to validate via verify-x509-name; or using "subject" instead, and requiring the use of a fully-formed DN in the dialog.
I think this should be "Won't Fix". It's unfortunate that we are stuck dealing with this fallout in the release, but there doesn't appear to be a foolproof way to transition configs (what is used for "tls-remote" currently is arbitrary, and can vary between installations).
This patch should not be applied as-is; as Chris mentions, the correct thing to do is to modify the settings in the VPN connection.
A valid workaround for n-m-openvpn would require also modifying either the value entered in the dialog to strip out part of the value (anything up and including "CN=") and keeping 'name' as the piece to validate via verify-x509-name; or using "subject" instead, and requiring the use of a fully-formed DN in the dialog.
I think this should be "Won't Fix". It's unfortunate that we are stuck dealing with this fallout in the release, but there doesn't appear to be a foolproof way to transition configs (what is used for "tls-remote" currently is arbitrary, and can vary between installations).