Bug 1628833 - nmcli can't establish VPN connection using passwd-file
Summary: nmcli can't establish VPN connection using passwd-file
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Haller
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1628946
TreeView+ depends on / blocked
 
Reported: 2018-09-14 07:09 UTC by Viktor Ashirov
Modified: 2020-11-24 20:18 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1628946 (view as bug list)
Environment:
Last Closed: 2020-11-24 20:18:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Viktor Ashirov 2018-09-14 07:09:12 UTC
Description of problem:
After upgrade to F29 I can no longer establish VPN connection using passwd-file, because the format has changed from 'vpn.secrets.password:' to 'vpn.secret.password:'.

Version-Release number of selected component (if applicable):
NetworkManager-1.12.2-2.fc29.x86_64
NetworkManager-openvpn-1.8.4-2.fc29.x86_64

How reproducible:
always

Steps to Reproduce:
1. Setup OpenVPN connection with connection-type = password, password-flags = 2
2. nmcli con up id "OpenVPN" passwd-file /path/to/pwdfile


Actual results:
$ nmcli con up id "OpenVPN" passwd-file /path/to/pwdfile
A password is required to connect to 'OpenVPN'.
Warning: password for 'vpn.secret.password' not given in 'passwd-file' and nmcli cannot ask without '--ask' option.
Error: Connection activation failed: No valid secrets

$ nmcli con show "OpenVPN" | grep vpn.secret
vpn.secrets:                            <hidden>

$ cat /path/to/pwdfile
vpn.secrets.password:hunter2


Expected results:
VPN connection should be established successfully.

Additional info:
If I change the contents of pwdfile to be
vpn.secret.password:hunter2

it works. But this is a regression from the previous version and it breaks backward compatibility.

Comment 1 Thomas Haller 2018-09-14 09:47:07 UTC
fix here: https://github.com/NetworkManager/NetworkManager/pull/201

Comment 3 Ben Cotton 2019-08-13 17:03:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 4 Ben Cotton 2019-08-13 19:44:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 5 Ben Cotton 2020-11-03 15:02:28 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2020-11-24 20:18:20 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.