Bug 973162
Summary: | SELinux is preventing /usr/libexec/nm-openvpn-service from 'open' accesses on the file /media/realcrypt1/Kunden/Focke/config/capri-ms@62.225.178.78/62.225.178.78.user.key. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Markus Schulze <ms> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | dcbw, dominick.grift, dwalsh, mgrepl, ms |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:d63019009df112e2cee38fc4dc6f7b2c4366008741405575be89c662dead3308 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-05 21:45:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Markus Schulze
2013-06-11 12:03:27 UTC
*** Bug 973163 has been marked as a duplicate of this bug. *** When I get an openvpn config package, containing all required files to establish a vpn to the site where this config comes from, I would expect that all files get the correct permissions when I import them with the NetworkManager vpn config import wizard. Either the wizard should copy the files to the correct location, or set the correct permissions. Should this issue be relayed to the NetworkManager maitainers ? You will need to fix labeling # chcon -R -t mnt_t /media/realcrypt1 and then you will add additional AVC msgs which you will need to allow to make this working. Basically this is not standard location for keys. And yes, the wizard should tell you what is the proper location. We probably want to allow NetworkManager to read file_t since this seems like it could be a common occurance. A usb stick with no labels used to transfer keys. Markus if you run in permissive mode, do you get additional avc messages? Daniel I did a very short test in permissive mode and got avc messages again. I think they were the same. I hope to have more time to test in the next days. When I correct the lables of the files contained in an openvpn-package to home_cert_t:s0 everything is fine. I could imagine, when a user imports a vpn configuration, it would be strait foreward for him, when the import wizard takes care of either the corret location for the files to put to, and/or sets the proper lables on them. Should a feature request or a bug be opened for the network-manager team ? Well we now allow this in F19, not sure Miroslav has back ported it to F18 yet. In order for this to work NetworkManager has to be allowed to read content without labels on it. Yes, has been back ported. commit b19632fb7da9a52aaed5bbfb9907155247f31bee Author: Miroslav Grepl <mgrepl> Date: Mon Jun 24 12:14:53 2013 +0200 Allow NM to read file_t (usb stick with no labels used to transfer keys for example) http://koji.fedoraproject.org/koji/buildinfo?buildID=429804 This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. |