[SOLVED] How to know if it's safe?

[OneOfFed]

Hello, after installing Fedora 16, I got a notification which tell me that SELinux is preventing /bin/systemctl from read access on the file cgroup.procs. Should I allow this acces or not? How to know what should I allow?
Note: I'm new to Linux.

[DBelton]

That looks like a bug in the selinux context someplace.

systemctl (systemd) is what creates the cgroups in the first place, so yes, it should have read access to it.

I would file a bug report on that one.

You can file a bug report at
http://bugzilla.redhat.com

Edit:

Just a thought.. Have you done any updates after you did your F16 install?

If not, do a full update and see if the SELinux contexts get updated and if that corrects your issue. I would try that before thinking about filing any bug reports.

[OneOfFed]

Originally Posted by DBelton

That looks like a bug in the selinux context someplace.
Just a thought.. Have you done any updates after you did your F16 install?

If not, do a full update and see if the SELinux contexts get updated and if that corrects your issue. I would try that before thinking about filing any bug reports.

Hello, I'll update it but even after update the alert will remail. So after updating, I'll delete it and see if it'll appear again, right? Will this blocked file affect updating?

[sea]

You can click on the black-yellowish icon in systray, on the dialog window that appears, select to trouble shoot it.
* You think systemctl is allowed to access XY.
* For each field on the right hand side you
* Copy paste the (usualy) last 2 lines (without the starting #) into a terminal, where you had loged into su. (the # indicates that the command requires root access (su/sudo))
* wait for the command to have finished
* Continue with the next lower field (last 2 lines)

This procedure may happen mostly after you have installed something new, that requires deep system access.
This may be, but not limited to:
* webserver
* mysql (or other databases)
* systemctl (part of get your system booting)
* ssh or other simliar internet tools

However, dont just allow everything showing up, but these are the most cases it should occour.
Better ask again, than allow malware to get system access

Hope this helps

[OneOfFed]

I allowed the file and updated Fedora. Then SELinux's preventing /usr/sbin/sendmail.sendmail from read access on the directory /home/sherif.