Bug 384293 - plasma-nm fails to correctly import from an openvpn config file
Summary: plasma-nm fails to correctly import from an openvpn config file
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_networkmanagement (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-02 19:24 UTC by Arash B
Modified: 2024-12-23 18:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Contains an openvpn config file and a crt file (1.52 KB, application/zip)
2017-09-02 19:24 UTC, Arash B
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arash B 2017-09-02 19:24:52 UTC
Created attachment 107657 [details]
Contains an openvpn config file and a crt file

plasma-nm fails to correctly import settings from an openvpn config file. Specifically it doesn't correctly import the security settings in the advanced properties. Connecting to the VPN server through the widget fails afterwards.

PREPARATION FOR REPRODUCING THE BUG

Download the two attached files from this bug report and put them in the same folder

STEPS TO REPRODUCE THE BUG

1. Open the "Networks" widget from the Task Manager by clicking on the widget (the widget's icon on the Task Manager is a wifi-symbol on most systems)

2. Click the "Configure the network connections..." in the top right of the widget window

3. Click the "Add new connection" in the bottom left of the new window

4. Select the "Import VPN connection..." from the bottom of the list and click the "Create" button

5. Browse to the file "UK London.ovpn" and click the "Open" button

6. Click the "No" button in the "Copy certificates - System Settings Module" window that pops up

7. Fill in a random username and password in the text fields "Username" and "Password" in the "Connections - System Settings Module" window

8. Click the "Apply" button in the same window

9. Open the "Networks" widget from the Task Manager

10. Click the "Connect" button next to the VPN connection "UK London"


EXPECTED RESULT

Connection to the VPN server is established (given that a valid username and password are provided)

ACTUAL RESULT

The procedure fails silently and without any GUI indication of failure at all. The command "journalctl -u NetworkManager -b 0" in a terminal shows the following lines in the end of the log file:

sep 02 19:36:16 usernameXYZ NetworkManager[1104]: <info>  [1504373776.3486] audit: op="connection-activate" uuid="cc6019ad-9e98-4b18-a9f5-e09695491b53" name="UK London" pid=1667 uid=1000 result="success"
sep 02 19:36:16 usernameXYZ NetworkManager[1104]: <info>  [1504373776.3562] vpn-connection[0x123f610,cc6019ad-9e98-4b18-a9f5-e09695491b53,"UK London",0]: Started the VPN service, PID 29771
sep 02 19:36:16 usernameXYZ NetworkManager[1104]: <info>  [1504373776.3799] vpn-connection[0x123f610,cc6019ad-9e98-4b18-a9f5-e09695491b53,"UK London",0]: Saw the service appear; activating connection
sep 02 19:36:16 usernameXYZ NetworkManager[1104]: <warn>  [1504373776.4004] vpn-connection[0x123f610,cc6019ad-9e98-4b18-a9f5-e09695491b53,"UK London",0]: VPN connection: failed to connect: 'Invalid HMAC auth.'
sep 02 19:36:16 usernameXYZ NetworkManager[1104]: <info>  [1504373776.4014] vpn-connection[0x123f610,cc6019ad-9e98-4b18-a9f5-e09695491b53,"UK London",0]: VPN plugin: state changed: stopped (6)
lines 1057-1080/1080 (END)

WORKAROUND

1. Select the VPN connection in the "Connections - System Settings Module" window (open it by clicking the top right button in the widget)

2. Click the "Advanced..." button

3. Click the "OK" button in the new window

4. Click the "OK" or "Apply" button in the "Connections - System Settings Module" window

WORKAROUND RESULT

Now you can connect to the VPN server through the VPN connection in the widget. The workaround procedure clearly overwrites faulty values that were written during the importing of data values from the config file.
Comment 1 Arash B 2017-09-02 19:31:44 UTC
It is noteworthy that in the openvpn connection's advanced settings the setting "Cipher" isn't set to anything. The advanced settings can be reached by clicking the "Advanced..." button once you have selected the openvpn connection from the configuration window. The "Cipher" setting is under the "Security" tab. The dropdown menu of the "Cipher" setting is blank, while the attached openvpn config file clearly states "cipher aes-128-cbc" on a line.

So this is probably a minor but separate bug.
Comment 2 Dennis Schridde 2018-12-28 13:53:37 UTC
I think this stems from the root cause of not using the NetworkManager OpenVPN importer, which bug #396530 deals with.
Comment 3 Justin Zobel 2023-01-19 00:19:00 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-02-03 05:01:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-02-18 03:47:29 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!