search for: httpd_unifi

...script being perl or sh, and despite the errors the cgi executes correctly. 'sestatus' reports: httpd_builtin_scripting active httpd_disable_trans inactive httpd_enable_cgi active httpd_enable_homedirs inactive httpd_ssi_exec inactive httpd_tty_comm inactive httpd_unified inactive Either httpd_ssi_exec or httpd_unified have made no difference in those errors. When I deactivate mod_suexec and comment SuexecUserGroup in Apache configs, those errors stop appearing. So I think this problem has to do directly with selinux policy and mod_suexec. Could this...

postfixadmin setup.php is claiming: *Error: Smarty template compile directory templates_c is not writable.* *Please make it writable.* *If you are using SELinux or AppArmor, you might need to adjust their setup to allow write access.* This goes away with 'setenforce 0', so it is an SELinux issue. I have tried both: restorecon -Rv /usr/share/postfixadmin and chcon -R -t

On 02/21/2017 11:46 AM, Zdenek Sedlak wrote: > On 2017-02-21 17:30, Robert Moskowitz wrote: >> postfixadmin setup.php is claiming: >> >> *Error: Smarty template compile directory templates_c is not writable.* >> *Please make it writable.* >> *If you are using SELinux or AppArmor, you might need to adjust their >> setup to allow write access.* >>

On 12/28/2016 05:11 AM, Todor Petkov wrote: > On Wed, Dec 28, 2016 at 5:18 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: >> Which is why I wonder if there is some different config for the C7.3 version >> of apache. >> >> Or something with the C7-arm build... > Can you check for SELinux warnings/errors in /var/log/audit/audit.log? Good advice. As I

...Was caused by: One of the following booleans was set incorrectly. Description: Allow httpd to read user content Allow access by executing: # setsebool -P httpd_read_user_content 1 Description: Allow httpd to unified Allow access by executing: # setsebool -P httpd_unified 1 # setsebool -P httpd_read_user_content 1 ... and setting one of them fixed the problem. I don't see a bug filed for this. Can anyone else confirm that httpd_enable_homedirs doesn't work as it did before 7.3? I suspect it's not widely used and the bug may not have been noticed ye...

Hi, Here's a list of all the booleans I tweaked on my server running CentOS 7: $ sudo cat /etc/selinux/targeted/active/booleans.local # This file is auto-generated by libsemanage # Do not edit directly. named_write_master_zones=0 httpd_can_sendmail=1 httpd_unified=1 ftpd_full_access=1 httpd_can_network_connect=1 spamd_enable_home_dirs=1 How can I "reset" (in a manner of speaking) these booleans to their default value post-install? Ideally, the booleans.local file should be empty, but since it's auto-generated, there's not much sense in...

SELinux appears to be interfering with winbind's functionality. I have the lastest policy package installed: selinux-policy-targeted-1.17.30-2.149 which allegedly solves this problem according to the RedHat knowledge base, but clearly does not. I have to turn off SELinux by using setenforce 0 (permissive) to get winbind to work at all, and based on what I see in the log files,

...-> on httpd_disable_trans --> off httpd_enable_cgi --> on httpd_enable_ftp_server --> off httpd_enable_homedirs --> on httpd_read_user_content --> off httpd_rotatelogs_disable_trans --> off httpd_ssi_exec --> off httpd_suexec_disable_trans --> off httpd_tty_comm --> on httpd_unified --> on httpd_use_cifs --> off httpd_use_nfs --> off I've looked into /etc/httpd/conf/httpd.conf and conf.d/ files... Does anybody know what is wrong, how to find out? Regards Alex