Bug 1245379 - SELinux is preventing brcupsconfig3 from 'execute' accesses on the file /etc/ld.so.cache.
Summary: SELinux is preventing brcupsconfig3 from 'execute' accesses on the file /etc/...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 22
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ae467436a0ee80cad8ca6ee7ccd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-21 23:51 UTC by Vitaliy Paritskiy
Modified: 2016-07-19 20:33 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 20:33:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vitaliy Paritskiy 2015-07-21 23:51:24 UTC
Description of problem:
SELinux is preventing brcupsconfig3 from 'execute' accesses on the file /etc/ld.so.cache.

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

If you believe that brcupsconfig3 should be allowed execute access on the ld.so.cache file 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:
# grep brcupsconfig3 /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:cupsd_t:s0-s0:c0.c1023
Target Context                system_u:object_r:ld_so_cache_t:s0
Target Objects                /etc/ld.so.cache [ file ]
Source                        brcupsconfig3
Source Path                   brcupsconfig3
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           glibc-2.21-7.fc22.x86_64 glibc-2.21-7.fc22.i686
Policy RPM                    selinux-policy-3.13.1-128.6.fc22.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.0.8-300.fc22.x86_64 #1 SMP Fri
                              Jul 10 21:04:56 UTC 2015 x86_64 x86_64
Alert Count                   10
First Seen                    2015-07-22 00:48:51 WEST
Last Seen                     2015-07-22 00:48:51 WEST
Local ID                      9bdf7f75-3472-4861-843c-cd4646f4d8a1

Raw Audit Messages
type=AVC msg=audit(1437522531.775:689): avc:  denied  { execute } for  pid=8026 comm="brprintconflsr2" path="/etc/ld.so.cache" dev="dm-1" ino=392944 scontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:ld_so_cache_t:s0 tclass=file permissive=0


Hash: brcupsconfig3,cupsd_t,ld_so_cache_t,file,execute

Version-Release number of selected component:
selinux-policy-3.13.1-128.6.fc22.noarch

Additional info:
reporter:       libreport-2.6.1
hashmarkername: setroubleshoot
kernel:         4.0.8-300.fc22.x86_64
type:           libreport

Comment 1 Vitaliy Paritskiy 2015-07-23 14:13:03 UTC
Description of problem:
1 - Open a Doc (any kind), and print it;
2 - Doc is being prepared for printing;
3 - After being ready, SELinux warning pops-up;
4 - Sending Job to a printer;
5 - Printing's  complete.

Version-Release number of selected component:
selinux-policy-3.13.1-128.6.fc22.noarch

Additional info:
reporter:       libreport-2.6.1
hashmarkername: setroubleshoot
kernel:         4.0.8-300.fc22.x86_64
type:           libreport

Comment 2 Fedora End Of Life 2016-07-19 20:33:19 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.