https://bugs.kde.org/show_bug.cgi?id=365458
Bug ID: 365458
Summary: plasma editor doesn't save tls-auth info while
exporting vpn profile
Product: plasma-nm
Version: 5.7.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: editor
Assignee: lu...@kde.org
Reporter: jpalczew...@hotmail.com
CC: jgrul...@redhat.com
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.
--
You are receiving this mail because:
You are watching all bug changes.
