Bug 1832718 - [NetworkManager-openvpn-gnome] variable "User private key" not imported from OVPN file
Summary: [NetworkManager-openvpn-gnome] variable "User private key" not imported from ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-openvpn
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-07 07:36 UTC by Joachim Frieben
Modified: 2021-05-25 16:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 16:10:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joachim Frieben 2020-05-07 07:36:56 UTC
Description of problem:
After importing a valid OVPN config file, the "User private key" remains unset, and the connection cannot be saved.

Version-Release number of selected component (if applicable):
NetworkManager-openvpn-gnome-1.8.12-1.fc32

How reproducible:
Always

Steps to Reproduce:
1. Open VPN settings panel.
2. Import some valid OVPN file.

Actual results:
The "User private key" variable remains unset showing the value "none".

Expected results:
The "User private key" variable is set to the correct value.

Additional info:
- When importing indivudal PEM files, then the VPN connection can be saved and activated successfully. However, when opening the corresponding configuration panel again, then "User private key" shows the value "none". The connection cannot be saved or updated unless the corresponding PEM file has been selected again.
- This bug is a regression with respect to Fedora 31 for which valid OVPN configuration files can be imported flawlessly.

Comment 1 Alessio 2020-05-15 14:58:30 UTC
Same issue here.

Comment 2 Alessio 2020-05-15 15:00:18 UTC
(In reply to Alessio from comment #1)
> Same issue here.

In addition. If you add the key by hand, you are able to save the connection and it also work.
But if you open the configuration in order to make some changes, you have to define the User private key again in order to be able to save the configuration.

Comment 3 Alessio 2020-05-15 15:04:00 UTC
Probably this is tracked upstream https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/50

Comment 4 Alessio 2020-06-17 18:42:10 UTC
It seems that it has been fixed upstream https://gitlab.gnome.org/GNOME/libnma/-/commit/b09c4dc2a8d3d7d44b9fc7ec22d499b7641de8c5

Comment 5 Fedora Program Management 2021-04-29 16:24:24 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 2021-05-25 16:10:06 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.