In general, I really like the idea of SELinux. It conceptually allows you to specify users, roles, and types for files and then checks against those conditions when something tries to access the files. It will only allow users that match the user condition, roles that match the role condition, and types that match the type condition to actually proceed and work with the file.<\/p>\n
So, for example, if you a role of “web object” which the webserver account fills, and it tries to write data into some directory that is not fit for that role, say \/bin\/, the operation will fail and the would-be hacker can’t put their trojaned ls program or whatever in there. That is a good thing. <\/p>\n
The problem is that the SELinux system is really kind of complicated. If you don’t know that it is there, you will just have things failing mysteriously, especially if you add directories in places that aren’t set up with the system already. Running a webserver on one of my linux machines, I ran into this problem. It is particularly an issue when you are trying to use executable scripts on your web server. <\/p>\n
Here is an instance of a problem that I had: I copied some scripts over from a production machine to a dev machine so I could build some more functionality based on the existing scripts. They went into So that isn’t good. When I try to access the file, I get a 404, which isn’t really true: actually the file is there, but SELinux is preventing it from being used. So, what should I do? I need to make the files have the correct SELinux settings. First, I try setting the type of the file:<\/p>\n sudo chcon -t httpd_sys_script_exec_t \/var\/www\/cgi-bin\/* Oh, that’s no good. What’s a partial context? Looks like you need to specify all the attributes of the file. Usually the files already have some default attributes, so it is ok, but for some reason these guys have nothing. I don’t know why. But if we apply all of the attributes that we need:<\/p>\n sudo chcon system_u:object_r:httpd_sys_script_exec_t \/var\/www\/cgi-bin\/*<\/p><\/blockquote>\n And that fixed the problem. Also, if you need to know where SELinux error messages are, they are sometimes in \/var\/log\/messages, sometimes in dmesg output, and sometimes in \/var\/log\/audit\/audit.log or possible \/var\/log\/avc.log, depending on how your system is set up.<\/p>\n","protected":false},"excerpt":{"rendered":" In general, I really like the idea of SELinux. It conceptually allows you to specify users, roles, and types for files and then checks against those conditions when something tries to access the files. It will only allow users that match the user condition, roles that match the role condition, and types that match the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"_links":{"self":[{"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/posts\/236"}],"collection":[{"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/comments?post=236"}],"version-history":[{"count":0,"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/posts\/236\/revisions"}],"wp:attachment":[{"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/media?parent=236"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/categories?post=236"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fugutabetai.com\/blog\/wp-json\/wp\/v2\/tags?post=236"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\/var\/www\/cgi-bin\/, a normal place for scripts on my system. To find out the attributes they should have:
<\/code><\/p>\n$ ls -ldZ \/var\/www\/cgi-bin<\/code>drwxr-xr-x root root system_u:object_r:httpd_sys_script_exec_t:s0 \/var\/www\/cgi-bin<\/code><\/code>$ ls -ldZ \/var\/www\/cgi-bin\/my.cgi-rwxr-xr-x root root \/var\/www\/cgi-bin\/my.cgi<\/p><\/blockquote>\n
chcon: can’t apply partial context to unlabeled file \/var\/www\/cgi-bin\/<\/p><\/blockquote>\n