Bug 770732 - SELinux is preventing /usr/sbin/pcscd from read, write access on the chr_file 026.
Summary: SELinux is preventing /usr/sbin/pcscd from read, write access on the chr_file...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bad35f01b8cf0d330c56fd7fca8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-28 17:49 UTC by Juan Orti
Modified: 2012-03-15 15:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-15 15:24:18 UTC
Type: ---


Attachments (Terms of Use)

Description Juan Orti 2011-12-28 17:49:33 UTC
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.1.6-1.fc16.x86_64
reason:         SELinux is preventing /usr/sbin/pcscd from read, write access on the chr_file 026.
time:           mié 28 dic 2011 18:47:58 CET

description:
:SELinux is preventing /usr/sbin/pcscd from read, write access on the chr_file 026.
:
:*****  Plugin device (91.4 confidence) suggests  *****************************
:
:If desea permitir que pcscd tenga read write acceso al 026 chr_file
:Then necesita modificar la etiqueta en  026 con el tipo de un dispositivo similar.
:Do
:# semanage fcontext -a -t SIMILAR_TYPE '026'
:# restorecon -v '026'
:
:*****  Plugin catchall (9.59 confidence) suggests  ***************************
:
:If cree que de manera predeterminada, pcscd debería permitir acceso read write sobre  026 chr_file.     
:Then debería reportar esto como un error.
:Puede generar un módulo de política local para permitir este acceso.
:Do
:permita el acceso momentáneamente executando:
:# grep pcscd /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:
:Additional Information:
:Source Context                system_u:system_r:pcscd_t:s0
:Target Context                system_u:object_r:device_t:s0
:Target Objects                026 [ chr_file ]
:Source                        pcscd
:Source Path                   /usr/sbin/pcscd
:Port                          <Desconocido>
:Host                          (removed)
:Source RPM Packages           pcsc-lite-1.7.4-6.fc16
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-67.fc16
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.1.6-1.fc16.x86_64 #1 SMP Wed
:                              Dec 21 22:41:17 UTC 2011 x86_64 x86_64
:Alert Count                   38
:First Seen                    dom 11 dic 2011 20:07:08 CET
:Last Seen                     mié 28 dic 2011 18:25:30 CET
:Local ID                      081245a0-d43c-40fe-969d-c3897f2ad174
:
:Raw Audit Messages
:type=AVC msg=audit(1325093130.885:421272): avc:  denied  { read write } for  pid=1115 comm="pcscd" name="026" dev=devtmpfs ino=3964542 scontext=system_u:system_r:pcscd_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file
:
:
:type=SYSCALL msg=audit(1325093130.885:421272): arch=x86_64 syscall=open success=no exit=EACCES a0=7f6303631410 a1=2 a2=7f6303631424 a3=4c items=0 ppid=1 pid=1115 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=pcscd exe=/usr/sbin/pcscd subj=system_u:system_r:pcscd_t:s0 key=(null)
:
:Hash: pcscd,pcscd_t,device_t,chr_file,read,write
:
:audit2allow
:
:#============= pcscd_t ==============
:allow pcscd_t device_t:chr_file { read write };
:
:audit2allow -R
:
:#============= pcscd_t ==============
:allow pcscd_t device_t:chr_file { read write };
:

Comment 1 Daniel Walsh 2011-12-29 17:44:42 UTC
Did pcscd actually work?  How did you trigger this?  Did you plugin a smart card and this AVC happens?


Note You need to log in before you can comment on or make changes to this bug.