Bug 1144847 - SELinux is preventing /usr/sbin/setfiles from 'mac_admin' accesses on the capability2 .
Summary: SELinux is preventing /usr/sbin/setfiles from 'mac_admin' accesses on the cap...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1dc43931c1cd6f76536841a3456...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-21 13:42 UTC by Shintaro Fujiwara
Modified: 2015-06-29 22:38 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:38:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Shintaro Fujiwara 2014-09-21 13:42:39 UTC
Description of problem:
yum update
SELinux is preventing /usr/sbin/setfiles from 'mac_admin' accesses on the capability2 .

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

If setfiles に、  capability2 の mac_admin アクセスがデフォルトで許可されるべきです。   
Then バグとして報告してください。 
ローカルのポリシーモジュールを生成すると、
 このアクセスを許可することができます。
Do
このアクセスを一時的に許可するには、以下を実行してください。
# grep restorecon /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023
Target Context                unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023
Target Objects                 [ capability2 ]
Source                        restorecon
Source Path                   /usr/sbin/setfiles
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           policycoreutils-2.2.5-4.fc20.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-182.fc20.noarch selinux-
                              policy-3.12.1-183.fc20.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.15.10-201.fc20.x86_64 #1 SMP Wed
                              Aug 27 21:10:06 UTC 2014 x86_64 x86_64
Alert Count                   4
First Seen                    2014-02-20 00:11:29 JST
Last Seen                     2014-09-21 22:28:17 JST
Local ID                      0a51e340-8e41-42fb-8c41-4c3d3d7fee6f

Raw Audit Messages
type=AVC msg=audit(1411306097.366:592): avc:  denied  { mac_admin } for  pid=20397 comm="restorecon" capability=33  scontext=unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023 tcontext=unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023 tclass=capability2


type=SYSCALL msg=audit(1411306097.366:592): arch=x86_64 syscall=lsetxattr success=no exit=EINVAL a0=7f62491a5de0 a1=7f624829d56e a2=7f62491a74f0 a3=29 items=0 ppid=19801 pid=20397 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=1 comm=restorecon exe=/usr/sbin/setfiles subj=unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023 key=(null)

Hash: restorecon,setfiles_t,setfiles_t,capability2,mac_admin

Additional info:
reporter:       libreport-2.2.3
hashmarkername: setroubleshoot
kernel:         3.15.10-201.fc20.x86_64
type:           libreport

Potential duplicate: bug 714136

Comment 1 Miroslav Grepl 2014-09-22 07:07:00 UTC
This looks like you are attempting to put down labels that the kernel does not understand.

Did you define own label?

Could you try to execute

# yum reinstall selinux-policy-targeted

and see if anything breaks.

Comment 2 Daniel Walsh 2014-09-24 12:26:23 UTC
Were you using a tool to build a different image like livecdtools?

Comment 3 Shintaro Fujiwara 2014-10-28 13:59:27 UTC
1

I resinstalled selinux-policy-targeted.

Nothing had been broken.

2

I did not use a tool to build a different image.

Comment 4 Daniel Walsh 2015-01-02 22:13:53 UTC
This avc would happen if restorecon was run without the kernel understanding the policy.  It means a label is being applied that does not exist in the kernel.

Comment 5 Fedora End Of Life 2015-05-29 12:56:02 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2015-06-29 22:38:15 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.