
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
The Web Server
|
323
Logs can reveal sensitive information in the URLs (GET parameters) and in the refer-
rer. An attacker with write access can plant cross-site scripting bugs that would be
triggered by a log analyzer as it processes the URLs.
Logs also grow like crazy and fill up the disk. One of the more common ways to
clobber a web server is to fill up the disk with logfiles. Use logrotate to rotate them
daily, or less often if your server isn’t that busy.
Setup Time: Configuring Apache
Configuring a web server is like configuring an email or DNS server—small changes
can have unforeseen consequences. Most web security problems are caused by con-
figuration errors rather than exploits of the Apache code.
Apache configuration files
I mentioned that Apache’s configuration files could be found under /etc/httpd/conf, /usr/
local/apache/conf, or some less well-lit place. The most prominent file is httpd.conf, but
in 1.3, you will also see access.conf and srm.conf. These are historic remnants from the
original NCSA web server. Only httpd.conf is used for Apache 2.0.
To keep local changes together, you can use a separate file like mystuff.conf and pro-
cess it with the
Include directive:
Include mystuff.conf
In Apache 2.0, you can specify a directory, and all files in it will be processed in
alphabetical ...