Bug 1371247 - system_u:system_r:webalizer_t cannot write to system_u:object_r:webalizer_rw_content_t
Summary: system_u:system_r:webalizer_t cannot write to system_u:object_r:webalizer_rw_...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 17:14 UTC by numien
Modified: 2019-08-12 13:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 16:54:46 UTC
Type: Bug


Attachments (Terms of Use)

Description numien 2016-08-29 17:14:44 UTC
Description of problem:
SELinux seems to disallow Webalizer writing to webalizer_rw_content_t, which it does during its periodic updates. The fact "rw_content" is right in the name suggests to me that this is probably a bug.

I've done a full system relabel on reboot, so I doubt it's a mis-tagging issue. Both the source and target context in the audit log certainly appear to be correct.


Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-158.21.fc23.noarch


Additional info:
type=AVC msg=audit(1472456625.581:2393927): avc:  denied  { getattr } for  pid=23914 comm="webalizer" path="/var/www/usage/daily_usage_201608.png" dev="sda2" ino=201387377 scontext=system_u:system_r:webalizer_t:s0-s0:c0.c1023 tcontext=system_u:object_r:webalizer_rw_content_t:s0 tclass=file permissive=1
type=AVC msg=audit(1472456625.581:2393928): avc:  denied  { write } for  pid=23914 comm="webalizer" name="daily_usage_201608.png" dev="sda2" ino=201387377 scontext=system_u:system_r:webalizer_t:s0-s0:c0.c1023 tcontext=system_u:object_r:webalizer_rw_content_t:s0 tclass=file permissive=1
type=AVC msg=audit(1472456625.581:2393929): avc:  denied  { open } for  pid=23914 comm="webalizer" path="/var/www/usage/daily_usage_201608.png" dev="sda2" ino=201387377 scontext=system_u:system_r:webalizer_t:s0-s0:c0.c1023 tcontext=system_u:object_r:webalizer_rw_content_t:s0 tclass=file permissive=1
type=AVC msg=audit(1472456625.614:2393930): avc:  denied  { getattr } for  pid=23914 comm="webalizer" path="/var/www/usage/usage.png" dev="sda2" ino=201408395 scontext=system_u:system_r:webalizer_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:webalizer_rw_content_t:s0 tclass=file permissive=1
type=AVC msg=audit(1472456625.614:2393931): avc:  denied  { write } for  pid=23914 comm="webalizer" name="usage.png" dev="sda2" ino=201408395 scontext=system_u:system_r:webalizer_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:webalizer_rw_content_t:s0 tclass=file permissive=1
type=AVC msg=audit(1472456625.614:2393932): avc:  denied  { open } for  pid=23914 comm="webalizer" path="/var/www/usage/usage.png" dev="sda2" ino=201408395 scontext=system_u:system_r:webalizer_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:webalizer_rw_content_t:s0 tclass=file permissive=1

Comment 1 Fedora End Of Life 2016-11-25 09:32:35 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 2 numien 2016-12-03 10:25:12 UTC
This issue appears to persist in Fedora 24.

Comment 3 Fedora End Of Life 2017-07-25 22:43:53 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 4 Fedora End Of Life 2017-08-08 16:54:46 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.