Bug 1467018

Summary: SELinux is preventing chrony-helper from 'getattr' accesses on the directory /home/sheepdestroyer.
Product: [Fedora] Fedora Reporter: sheepdestroyer <sheepdestroyer>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: dominick.grift, dwalsh, lvrabec, mgrepl, plautrba, pmoore, sheepdestroyer, ssekidde, thiagoahauck
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bf5998d40a6a201ba2bf7a649e0e6769f28000016ff7b106abcba7e138fc4489;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:24:21 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 sheepdestroyer 2017-07-01 19:02:06 UTC
Description of problem:
just had updated
SELinux is preventing chrony-helper from 'getattr' accesses on the directory /home/sheepdestroyer.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that chrony-helper should be allowed getattr access on the sheepdestroyer directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'chrony-helper' --raw | audit2allow -M my-chronyhelper
# semodule -X 300 -i my-chronyhelper.pp

Additional Information:
Source Context                unconfined_u:system_r:chronyd_t:s0-s0:c0.c1023
Target Context                unconfined_u:object_r:user_home_dir_t:s0
Target Objects                /home/sheepdestroyer [ dir ]
Source                        chrony-helper
Source Path                   chrony-helper
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-259.fc26.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.11.7-300.fc26.x86_64 #1 SMP Mon
                              Jun 26 14:54:05 UTC 2017 x86_64 x86_64
Alert Count                   1
First Seen                    2017-07-01 20:53:49 CEST
Last Seen                     2017-07-01 20:53:49 CEST
Local ID                      53f96cbf-14db-4ea9-bd2b-3b02ffd29750

Raw Audit Messages
type=AVC msg=audit(1498935229.176:229): avc:  denied  { getattr } for  pid=2401 comm="chrony-helper" path="/home/sheepdestroyer" dev="sda10" ino=12582913 scontext=unconfined_u:system_r:chronyd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_dir_t:s0 tclass=dir permissive=0


Hash: chrony-helper,chronyd_t,user_home_dir_t,dir,getattr

Version-Release number of selected component:
selinux-policy-3.13.1-259.fc26.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.1
hashmarkername: setroubleshoot
kernel:         4.11.7-300.fc26.x86_64
type:           libreport

Comment 1 sheepdestroyer 2017-07-04 14:46:14 UTC
again and again since update

Comment 2 Daniel Walsh 2017-07-06 11:37:42 UTC
Not sure why chrony-helper is looking into the /home/sheepdestroyer home directory?

Comment 3 sheepdestroyer 2017-07-11 22:45:42 UTC
Description of problem:
was yum upgrading libreoffice

Version-Release number of selected component:
selinux-policy-3.13.1-259.fc26.noarch

Additional info:
reporter:       libreport-2.9.1
hashmarkername: setroubleshoot
kernel:         4.11.9-300.fc26.x86_64
type:           libreport

Comment 4 thiagoahauck 2017-09-02 16:34:59 UTC
Description of problem:
Não sei o que causou o problema ou porque esta notificação do SELinux fica aparecendo em meu desktop.
Esta notificação aparece para min a mais de 2 meses, formatei meu computador a pouco tempo e ainda continua.
I do not know what caused the problem or why this SELinux notification is showing up on my desktop.
This notification appears for min more than 2 months, I formatted my computer shortly and it still continues.

Version-Release number of selected component:
selinux-policy-3.13.1-260.6.fc26.noarch

Additional info:
reporter:       libreport-2.9.1
hashmarkername: setroubleshoot
kernel:         4.12.9-300.fc26.x86_64
type:           libreport

Comment 5 Fedora End Of Life 2018-05-03 08:05:22 UTC
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.

Comment 6 Fedora End Of Life 2018-05-29 11:24:21 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.