Bug 419609 - previously exported openvpn.conf importing fails on tls-auth key direction
Summary: previously exported openvpn.conf importing fails on tls-auth key direction
Status: RESOLVED FIXED
Alias: None
Product: plasma-nm
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-03 21:14 UTC by Gabor
Modified: 2023-01-20 01:56 UTC (History)
1 user (show)

See Also:
Latest Commit: https://invent.kde.org/plasma/plasma-nm/-/commit/9b22aa548f02ef43f7275ab2f9ffa48bde8a1ba8
Version Fixed In: 5.27

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor 2020-04-03 21:14:25 UTC 
STEPS TO REPRODUCE
1. export an openvpn connection which have this line: "tls-auth some.key 1"
2. rename the file
3. import it
4. try to connect

OBSERVED RESULT
in the log: NetworkManager[69064]: Options error: Unknown key direction ' 1' -- must be '0' or '1'
in the settings it shows 1
after set to 0 and back to 1 it started working
Comment 1 Nicolas Fella 2023-01-20 01:56:48 UTC 
In Plasma 5.27 we changed the VPN file import to closely match what nmcli does, so this should be fixed