Displaying 4 results from an estimated 4 matches for "httpd_tty_comm".
2011 Nov 01
1
SELinux and SETroubleshootd woes in CR
...#39;, 'allow_ftpd_anon_write', 'device',
'catchall_boolean', 'automount_exec_config', 'leaks', 'setenforce',
'ftpd_is_daemon', 'allow_zebra_write_config', 'firefox',
'nfs_export_all_ro', 'httpd_enable_cgi', 'httpd_tty_comm',
'public_content', 'ftp_home_dir', 'prelink_mislabled', 'allow_execstack',
'spamd_enable_home_dirs', 'sshd_root', 'samba_share_nfs',
'httpd_builtin_scripting', 'allow_ftpd_full_access', 'default',
'allow_ftpd_u...
2006 Sep 08
0
SELinux targeted + httpd + suexec
...----
This is independent of the 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 poli...
2008 Jun 03
1
SELinux and samba/winbind w/ADS on RHEL 4.6
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,
2010 Sep 29
5
Forbidden: can't access *.html files in /var/www/html
...off
httpd_can_sendmail --> 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