SELinux problems after F10->F11 upgrade in x86_64 system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

there have been a lot (well over 100 during the 1st 12 hours) of
dbusd-related SELinux denials after upgrading my x86_64 system from F10
to F11. In F10 and earlier SELinux problems were usually caused by
various fail2ban operations but now these denials - probably due to
updated fail2ban in F11  - are practically non-existent.

In F10 (and earlier) it was possible to get rid of SELinux denials by
compiling and installing a local module derived from
either /var/log/messages or /var/log/audit/audit.log, as explained in
SELinux FAQ.

However, the local module method doesn't seem to be effective in the
dbusd case - or I am doing something wrong. Compiling the local module
doesn't report any errors but installing it results in:

[root@mybox ~]# semodule -i local.pp
libsepol.print_missing_requirements: local's global requirements were
not met: type/attribute unconfined_t
libsemanage.semanage_link_sandbox: Link packages failed
semodule:  Failed!
[root@mybox ~]# 

After running 'touch /.autorelabel; reboot' I got rid of 'File label'
denials but the 'dbusd' ones are still there.

So what now?

TIA, Antti


-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux