Page 1 of 1

[Win7 host / Fedora 13 guest] abrtd issues

Posted: 2. Dec 2010, 11:10
by Pyrus
Hello,

I just installed Fedora 13 on my 3.2.10 VirtualBox's version and the first thing I see after logging in my session is an alert like this one:
SELinux is preventing /usr/sbin/abrtd "create" access on kerneloops-1291278208-1463-3

As I'm an unqualified user I searched over the internet and found nothing interesting about this (or I missed it)

Here is the messages' log and alert details:
"Persmission non accordée" meaning permission denied, not granted, ye i'm French ;)

Code: Select all

[root@nayeli ~]# grep abrtd /var/log/messages
Dec  2 09:21:27 nayeli abrtd: Registered Reporter plugin 'Logger'
Dec  2 09:21:27 nayeli abrtd: Registered Analyzer plugin 'Kerneloops'
Dec  2 09:21:27 nayeli abrtd: Registered Analyzer plugin 'Python'
Dec  2 09:21:27 nayeli abrtd: Registered Reporter plugin 'Bugzilla'
Dec  2 09:21:27 nayeli abrtd: Registered Analyzer plugin 'CCpp'
Dec  2 09:21:27 nayeli abrtd: Registered Reporter plugin 'KerneloopsReporter'
Dec  2 09:21:27 nayeli abrtd: Registered Action plugin 'KerneloopsScanner'
Dec  2 09:21:27 nayeli abrtd: Init complete, entering main loop
Dec  2 09:23:28 nayeli abrtd: Can't create lock file '/var/spool/abrt/kerneloops-1291278208-1461-3.lock': Permission non accordée
Dec  2 09:23:30 nayeli setroubleshoot: SELinux empêche l'accès en « create » à /usr/sbin/abrtd on kerneloops-1291278208-1461-3.lock. For complete SELinux messages. run sealert -l 60d11d5d-3a29-48c3-88b8-032b6d830a6b
e
For the alert details I can probably translate it to english correctly if needed, but that's a long enough work for me to make me wait your advisory first.

Code: Select all

[root@nayeli ~]# sealert -l 60d11d5d-3a29-48c3-88b8-032b6d830a6b

Résumé:

SELinux empêche l'accès en « create » à /usr/sbin/abrtd on
kerneloops-1291278208-1461-3.

Description détaillée:

SELinux a refusé l'accès demandé par abrtd. Il n'est pas prévu que cet accès
soit requis par abrtd et cet accès peut signaler une tentative d'intrusion. Il
est également possible que cette version ou cette configuration spécifique de
l'application provoque cette demande d'accès supplémenta

Autoriser l'accès:

Vous pouvez créer un module de stratégie locale pour autoriser cet accès - lisez
la FAQ (http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Merci de
remplir un rapport de bogue.

Informations complémentaires:

Contexte source               system_u:system_r:abrt_t:s0-s0:c0.c1023
Contexte cible                system_u:object_r:var_spool_t:s0
Objets du contexte            kerneloops-1291278208-1461-3.lock [ lnk_file ]
source                        abrtd
Chemin de la source           /usr/sbin/abrtd
Port                          <Inconnu>
Hôte                          nayeli.virtual-home
Paquetages RPM source         abrt-1.1.14-1.fc13
Paquetages RPM cible          
Politique RPM                 selinux-policy-3.7.19-73.fc13
Selinux activé                True
Type de politique             targeted
Mode strict                   Enforcing
Nom du plugin                 catchall
Nom de l'hôte                 nayeli.virtual-home
Plateforme                    Linux nayeli.virtual-home 2.6.34.7-61.fc13.x86_64
                              #1 SMP Tue Oct 19 04:06:30 UTC 2010 x86_64 x86_64
Compteur d'alertes            1
Première alerte               Thu Dec  2 09:23:28 2010
Dernière alerte               Thu Dec  2 09:23:28 2010
ID local                      60d11d5d-3a29-48c3-88b8-032b6d830a6b
Numéros des lignes            

Messages d'audit bruts        

node=nayeli.virtual-home type=AVC msg=audit(1291278208.50:19): avc:  denied  { create } for  pid=1461 comm="abrtd" name="kerneloops-1291278208-1461-3.lock" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_spool_t:s0 tclass=lnk_file

node=nayeli.virtual-home type=SYSCALL msg=audit(1291278208.50:19): arch=c000003e syscall=88 success=no exit=-13 a0=7fff9b72c260 a1=19ad238 a2=7fff9b72c264 a3=7fff9b72bfa0 items=0 ppid=1 pid=1461 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="abrtd" exe="/usr/sbin/abrtd" subj=system_u:system_r:abrt_t:s0-s0:c0.c1023 key=(null)
I don't know what others information you might need so let me know if you need some.

Thank you for your incoming help :)

Re: [Win7 host / Fedora 13 guest] abrtd issues

Posted: 2. Dec 2010, 11:44
by fixedwheel
Hello,
SELinux is preventing /usr/sbin/abrtd "create" access on kerneloops-1291278208-1463-3
thats a Fedora bug => https://bugzilla.redhat.com/show_bug.cgi?id=647982


if you don't need the SELinux feature then disable it, IMHO its a real PITA

Re: [Win7 host / Fedora 13 guest] abrtd issues

Posted: 3. Dec 2010, 21:41
by Pyrus
Oh .. ok thanks ... ! ^^