While exporting a VPN profile from a plasma editor, information like " tls-auth ta.key 1 " isn't present in exported file, what makes exported profile unusable(it just hangs at trying to connect - a try to use one from cli openvpn suggests no possible avoidance to MiTM attacks). Reproducible: Always Steps to Reproduce: 0. Create a VPN which needs a tls-auth key, as described in details section. 1. Create an VPN profile by hand, in nm-connection-editor "Connection"->"Add"->OpenVPN 2. Make sure that it works and sucessfully connects(i.e. key and proper direction is set in "Advanced" window) 3. Export it and import again. Actual Results: Imported profile doesn't have any info about tls-key. Expected Results: There should be a tls-auth line, as specifed above. Workaround is really simple(it's enough to tick correct option and select that key), however - it's just a unnecessary waste of time debugging what's wrong.
Git commit 48db82bc5b5801eeb7cbbad838cca6460a4afce5 by Lamarque V. Souza. Committed on 05/09/2016 at 13:25. Pushed by lvsouza into branch 'master'. Export tls-auth tag for the other connection types too. M +5 -3 vpn/openvpn/openvpn.cpp http://commits.kde.org/plasma-nm/48db82bc5b5801eeb7cbbad838cca6460a4afce5
Git commit 4eede9a350e36c84594952dd1f2c999c0d02d2ec by Lamarque V. Souza. Committed on 05/09/2016 at 13:31. Pushed by lvsouza into branch 'Plasma/5.7'. Export tls-auth tag for the other connection types too. FIXED-IN: 5.7.5 M +5 -3 vpn/openvpn/openvpn.cpp http://commits.kde.org/plasma-nm/4eede9a350e36c84594952dd1f2c999c0d02d2ec