importer incorrectly writes tls-crypt-v2 value as tls-crypt in vpn.data
When I import a .ovpn file that contains a <tls-crypt-v2>
block, the contents of the block are correctly written to a .pem file. (The file's name even ends with "tls-crypt-v2.pem".) However, that file's path is saved to the new connection's vpn.data property as "tls-crypt" instead of "tls-crypt-v2".
As a result, the VPN connection fails to activate, writing these cryptic messages to the system log:
starting openvpn
dbus: failure: connect-failed (1)
dbus: failure: connect-failed (1)
Manually editing the connection with nmcli connection edit
and rewriting that tls-crypt
value as tls-crypt-v2
allows the connection to activate.
However, the fixed setting doesn't show up in the GUI's TLS Settings tab, and the the GUI doesn't offer a Mode: TLS-Crypt-V2 option. (Only TLS-Auth and TLS-Crypt are offered.)
The changelog claims that tls-crypt-v2 support was added in version 1.8.14, but it seems that is incorrect, as I am using version 1.10.2.