Bug 1444607
Summary: | SELinux is preventing starter from execute_no_trans access on the file /usr/libexec/strongswan/charon. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrey Motoshkov <motoskov> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | avagarwa, dwalsh, lvrabec, mgrepl, plautrba, pmoore, pwouters, rc556677, redhat-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-24 15:21:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrey Motoshkov
2017-04-23 07:53:47 UTC
Still present: selinux-policy-3.13.1-259.fc26.noarch strongswan-5.5.3-1.fc26.x86_64 This my local policy to make StrongSWAN work again: module local 1.0; require { type ipsec_t; type ipsec_exec_t; type var_run_t; class file { execute_no_trans }; class sock_file { unlink write }; } #============= ipsec_t ============== allow ipsec_t ipsec_exec_t:file execute_no_trans; allow ipsec_t var_run_t:sock_file { unlink write }; This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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. |