Difference between revisions of "SELinux Notes"
From Simson Garfinkel
Jump to navigationJump to search
m |
m |
||
Line 7: | Line 7: | ||
* https://wiki.gentoo.org/wiki/SELinux/Tutorials/What_is_this_unconfined_thingie_and_tell_me_about_attributes | * https://wiki.gentoo.org/wiki/SELinux/Tutorials/What_is_this_unconfined_thingie_and_tell_me_about_attributes | ||
* https://stackoverflow.com/questions/5326531/php-warning-unknown-failed-to-open-stream | * https://stackoverflow.com/questions/5326531/php-warning-unknown-failed-to-open-stream | ||
* https://wiki.centos.org/HowTos/SELinux | |||
* https://www.lisenet.com/2016/advanced-apache-configuration-with-selinux-on-rhel-7/ | |||
==Problem: apache can't access the files== | ==Problem: apache can't access the files== |
Revision as of 06:33, 22 January 2019
SELinux is enabled by default on Centos 7 and on RHEL. It's a good thing to enable for internet-facing servers. It makes it far, far more complex to run a web server.
References:
- https://wiki.centos.org/HowTos/SELinux
- https://wiki.gentoo.org/wiki/SELinux/Tutorials/What_is_this_unconfined_thingie_and_tell_me_about_attributes
- https://stackoverflow.com/questions/5326531/php-warning-unknown-failed-to-open-stream
- https://wiki.centos.org/HowTos/SELinux
- https://www.lisenet.com/2016/advanced-apache-configuration-with-selinux-on-rhel-7/
Problem: apache can't access the files
sudo /sbin/restorecon -R /var/www
setsebool -P httpd_read_user_content 1
Running a web server:
If you can't run PHP, you may have the files in the wrong SELinux security context. You can change the security
- Use ls -lZ /var/www/html/xxx to check the security context
- You can give the web server read/write access to the files with:
chcon -R -t httpd_sys_rw_content_t /var/www/html/xxx
Disabling SELinux
- edit /etc/selinux/config and change SELINUX from 'enforcing' to 'permissive'