New answers tagged

0

sealert -l 92a5910b-1bfe-4b98-a2de-d773cce85051 will describe the exact cause, in the summary section you'll find the file name & the selinux context for fixing the issue execute the below command. chcon -t selinux_context 'file_name' A suggested command to allow access and resolve the denial. it gives the command to change the file1 type to ...


1

Your database contents, customized scripts, and configurations should be your top priority. A full system backup is always a good idea to make sure you're not forgetting any important stuff, or to do a quick recovery.


1

It may depend on which distribution you are using, but in Fedora (and therefore in most or all Fedora-derived distributions including Red Hat Enterprise Linux and CentOS) the selinux-policy-targeted package includes a postinstall script with restorecon and fixfiles commands, so it should not be necessary.


-1

Use echo 0 > /selinux/enforce on Centos.


2

SELinux context is stored in file's extended attributes (xattr, man 5 attr). Tools for working with them are available in core/attr package. Attributes, including SELinux context, can be retrieved with getfattr. There is a twist though: by default getfattr lists only attributes from user. namespace; and selinux attribute we need is in security namespace. So ...



Top 50 recent answers are included