mod_security

Apache module, to greatly increase the security of the webserver to protect it from badly written webapps. (for instance the high risc phpBB2).

Would be nice to see this is the list of modules that can be [en|dis]abled.

Here ya go:

  foo_module   	

Disabled
cgi_module
Enabled
cgid_module
Enabled
access_module
Enabled
auth_module
Enabled
auth_anon_module
Enabled
auth_dbm_module
Enabled
auth_digest_module
Enabled
cache_module
Enabled
disk_cache_module
Enabled
mem_cache_module
Enabled
ext_filter_module
Enabled
include_module
Enabled
deflate_module
Enabled
log_config_module
Enabled
env_module
Enabled
mime_magic_module
Enabled
cern_meta_module
Enabled
expires_module
Enabled
headers_module
Enabled
usertrack_module
Enabled
unique_id_module
Enabled
setenvif_module
Enabled
proxy_module
Enabled
proxy_connect_module
Enabled
proxy_ftp_module
Enabled
proxy_http_module
Enabled
mime_module
Enabled
dav_module
Enabled
status_module
Enabled
autoindex_module
Enabled
asis_module
Enabled
info_module
Enabled
suexec_module
Enabled
dav_fs_module
Enabled
vhost_alias_module
Enabled
negotiation_module
Enabled
dir_module
Enabled
imap_module
Enabled
actions_module
Enabled
speling_module
Enabled
userdir_module
Enabled
alias_module
Enabled
rewrite_module
Enabled

As I recall Mod_Securyty is available in the experemtnal RPM archive, or at least there used to be. In any event youc an install it yourself fromsource if you want.

You can install mod_security now and manually config it warp3 but let me explain the problem about the Apache page if you’ve done so and aren’t seeing the module.

InterWorx-CP (right now) parses only the /etc/httpd/conf/httpd.conf file to look for modules. It can (and will at some point) do other files in /etc/httpd/conf.d like the security.conf that is bundled with most apache module RPMs.

We will probably (no eta) make an easy interface to mod_security at some point as well and fix the above parsing deficiency.

Chris