Bug 1569235 - Importing openvpn file needs to move cert files to ~/.cert/ to work with SELinux
Summary: Importing openvpn file needs to move cert files to ~/.cert/ to work with SELinux
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 29
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-18 20:48 UTC by Hayden
Modified: 2019-11-27 19:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 19:36:48 UTC
Type: Bug

Attachments (Terms of Use)

Description Hayden 2018-04-18 20:48:01 UTC
Description of problem:

You can import .opvn OpenVPN VPN configuration files that often come with a CA cert and TLS cert using gnome-control-center.

If you simply import those files and leave the CA cert where it is, say ~/Downloads with the opvn and TLS cert, (1) the imported config breaks if you delete those files-they aren't actually saved anywhere, and (2) SELinux will not let you use the CA Cert outside ~/.cert/, causing deep frustration. See: https://ask.fedoraproject.org/en/question/67927/how-to-understand-an-selinux-file-permission-denied-issue/

There are also no alerts when this happens in SELinux troubleshooter.

Version-Release number of selected component (if applicable): 3.28.1

How reproducible: Highly


Steps to Reproduce:
1. Import OpenVPN configuration from OPVN
2. Configure with a ca crt outside of ~/.cert/
3. Try to connect

Actual results:

You cannot connect.

OpenSSL: error:0200100D:system library:fopen:Permission denied
Cannot load CA certificate file /home/hayden/.vpn/vpn-se1.ca.crt (no entries were read)

Expected results:

The opvn and related certs get imported somewhere and SELinux is updated to bless those certs.

Comment 1 Jan Kurik 2018-08-14 10:06:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 2 Joachim Frieben 2018-10-05 14:24:43 UTC
I have noticed that gnome-control-center does not accept any TLS related directive for an OpenVPN connection when the TLS-key/-certificate files are located in some system directory $CERTROOT/certs/ whereas the CA certificate, the user certificate, and the user key are imported successfully from individual files in the same directory. All files are labelled identically and exhibit the same file permissions. The same set-up works as expected for Fedora 28.

Comment 3 Joachim Frieben 2018-10-16 14:50:39 UTC
(In reply to Joachim Frieben from comment #2)
Current Fedora 28 is now affected by this issue, too.

Comment 4 Ben Cotton 2019-10-31 20:38:16 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 5 Ben Cotton 2019-11-27 19:36:48 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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

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.