Bug 922732
Summary: | SELinux prevents openvpn_t to write inside the /var/lib/openvpn directory | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Michal Bruncko <michal.bruncko> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Michal Trunecka <mtruneck> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | dwalsh, ebenes, mmalik, mtruneck, redhatbugzilla |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.7.19-210.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-21 10:20:35 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: | |||
Bug Depends On: | 922786 | ||
Bug Blocks: | 985435 |
Description
Michal Bruncko
2013-03-18 11:45:14 UTC
It looks more as openvpn bug for now. We have the following labeling /etc/openvpn(/.*)? gen_context(system_u:object_r:openvpn_etc_t,s0) /etc/openvpn/ipp.txt -- gen_context(system_u:object_r:openvpn_etc_rw_t,s0) /etc/rc\.d/init\.d/openvpn -- gen_context(system_u:object_r:openvpn_initrc_exec_t,s0) /usr/sbin/openvpn -- gen_context(system_u:object_r:openvpn_exec_t,s0) /var/log/openvpn.* gen_context(system_u:object_r:openvpn_var_log_t,s0) /var/run/openvpn(/.*)? gen_context(system_u:object_r:openvpn_var_run_t,s0) So if a new dir is needed then it needs to be added to RPM payload and we will need to add labeling. Hi Miroslav, Should I open a new bugreport for addressing missing directory for openvpn component? Thanks I've raised #922786 for openvpn component. Ok. I added support for /var/lib/openvpn *** Bug 789342 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1598.html |