Archive for the ‘apache’ Category

Rails Error: Malformed header from script

August 6, 2008

If you are running your rails app on an Apache2+ mod_fcgid set up and you receive errors like

[Fri Aug 1 08:10:06 2008 [error] [client 111.222.333.444] malformed header from script. Bad header=*******: dispatch.fcgi

in the Apache error log, make sure you don’t have any output to console (like ‘puts’, added for debugging) left in the code.

Whatever the script output goes to the header section of the response and most of the times Apache won’t understand it.

Removing “puts” from the code helped me fix it.

List all the loaded modules :: apache

June 12, 2008

You can use the following command to list all the loaded modules in apache (both DSO and Static)
———-

apachectl -t -D DUMP_MODULES

———-

The output will be something like
———
dir_module (static)
actions_module (static)
userdir_module (static)
alias_module (static)
rewrite_module (static)
so_module (static)
auth_passthrough_module (shared)
bwlimited_module (shared)
php5_module (shared)
fcgid_module (shared)
proxy_module (shared)
———

Mod Security 2 Default Rules and IDs

June 8, 2008

Here is the Mod Security 2 Default Rules and IDs. May be useful if you want to deactivate any specific rule.
————————————–
marketing.conf

10005 – Marketing Default Action
10006 – Google robot activity
10007 – Yahoo robot activity
10008 – MSN robot activity

http_policy.conf

60031 – HTTP Policy Default Action
60032 – Allow only POST,GET,HEAD Requests
60033 – Block CONNECT / TRACE Requests
60010 – Restrict Content Types For Posts
60034 – Restrict HTTP Protocol Versions
60035 – File extension request restrictions
60036 – Allow Only Certain Extensions

generic_attacks.conf

50002 – Generic Attacks Default Action
50009 – Session Fixation Cookie Mangling ?
50007 – Blind SQL Injection Attack
50903 – Blind SQL Injection Attack
50904 – Blind SQL Injection Attack
50001 – SQL Injection Attack
50905 – SQL Injection Attack
50906 – SQL Injection Attack
50004 – Cross-site Scripting (XSS) Attack
50005 – Remote File Access Attempt
50002 – System Command Access
50006 – System Command Injection
50008 – Injection of Undocumented ColdFusion Tags
50010 – LDAP Injection Attack
50011 – SSI injection Attack
50013 – PHP Injection Attack

bad_robots.conf

90900 – Bad Robots Default Action
90002 – Block Known Bot Scanners
90901 – Block Known Bot Scanners
90902 – Block Known Bot Scanners
90012 – Rogue Site Crawlers
90011 – Automated Site Crawler

outbound.conf

70001 – Outbound Filter Default Action
70002 – Statistic Software Information Leak
70003 – SQL Information Leakage
70004 – IIS Information Leakage
70007 – Zope Information Leakage
70008 – Cold Fusion Information Leakage
70009 – PHP Information Leakage
70010 – ISA server existence revealed
70012 – Microsoft Word document properties leakage
70013 – Directory Listings Turned OFF !!
70011 – File or Directory Names Leakage
70014 – ASP/JSP source code leakage
70903 – ASP/JSP source code leakage
70015 – PHP source code leakage
70016 – Cold Fusion source code leakage
70901 – IIS Application Not Available
70118 – IIS Application Not Available

protocol_violations.conf

60007 – Protocol Violations Default Action
60008 – Request Missing a Host Header
60009 – Request Missing a User Agent Header
60015 – Request Missing an Accept Header
60016 – Non Numeric Content-Length Header
60017 – Host header is a numeric IP address
60011 – Block GET or HEAD requests with bodies
60012 – POST request must have a Content-Length header
60013 – ModSecurity does not support transfer encodings
50107 – URL Encoding Abuse Attack
50801 – UTF8 Encoding Abuse Attack
60014 – Proxy access attempt
60015 – Request Missing an Accept Header Byte Range
60901 – Localized Byte Range Check

trojans.conf

50920 – Trojans Default Action
50111 – Possible malicious file upload
50921 – Possible malicious file upload
50922 – Possible malicious file upload

Got root rule ids

Got Root Mod Security 2 Rules – /gotroot/

apache2-rules.conf

400050 – Apache 2 Rules Default Action

jitp.conf

300051 – Just In Time Patches Default Action
390000 – Awstats.pl probe
390080 – Tests For Valid X-Forwarded Header

jitp2.conf

300051 – Just In Time Patches Default Action
390000 – Awstats.pl probe
390070 – Generic phpbb_root_path exploit
390075 – Generic mosConfig_absolute_path File Inclusion Vulnerability
390076 – Generic mosConfig_absolute_path File Inclusion Vulnerability
390083 – tikiwiki XSS Vulnerability
390082 – tikiwiki Remote File Inclusion Vulnerability
390039 – vwar_root remote/local file inclusion
390001 – aWebBB XSS attack on post.php
390002 – aWebBB XSS attack on editac.php
390003 – aWebBB XSS attack on register.php
390004 – aWebBB XSS attack / aWebBB SQL attack
390005 – aWebBB SQL attack
390006 – phpBB cur_password XSS attack
390007 – PHPNuke-Clan 3.0.1 Remote File Inclusion Exploit
390008 – Claroline <= 1.7.4 scormExport.inc.php remote command vuln
390009 – Claroline <= 1.7.4 scormExport.inc.php remote command vuln
390010 – Claroline <= 1.7.4 XSS attack
390011 – aWebNews XSS attack
390012 – aWebBBNewsSQL attack
390013 – aWebBBNewsSQL attack
390014 – aWebAPP XSS attack
390015 – qliteNEws SQL injection attack
390016 – RedCMS SQL Injection
390017 – RedCMS SQL Injection
390018 – RedCMS XSS attack
390019 – Oxygen SQL Injection
390020 – Mantis XSS attack
390021 – Oxygen SQL Injection
390022 – Mantis XSS attack
390023 – PHPCollab v2.x / NetOffice v2.x sendpassword.php SQL Injection
390024 – Sourceworkshop newsletter SQL Injection Vulnerability
390025 – X-Changer SQL Injection Vulnerability
390025 – X-Changer SQL Injection Vulnerability
390026 – X-Changer XSS Vulnerability
390027 – Null news Multiple SQL Injection Vulnerabilities
390028 – Null news Multiple SQL Injection Vulnerabilities
390029 – Null news Multiple SQL Injection Vulnerabilities
390030 – PHPLiveHelper 1.8 remote command execution Xploit
390031 – Pixel Motion Blog SQL Injection Vulnerabilities
390032 – Pixel Motion Blog SQL Injection Vulnerabilities
390033 – Nuked-Klan SQL Injection Vulnerability
390035 – TFT Gallery passwd Exposure of User Credentials
390036 – Nuked-Klan SQL Injection Vulnerability
390037 – WEBalbum Local File Inclusion Vulnerability
390038 – G-Book g_message Script Insertion Vulnerability
390039 – PHPMyChat exploit
390040 – Horde Help Module Remote Execution
390041 – Internet PhotoShow Remote File Inclusion Exploit
390042 – Censtore.cgi exploit
390043 – quizz.pl exploit
390044 – phpinfo.cgi command execution
390045 – phpRaid phpbb_root_path File Inclusion Vulnerability
390046 – openEngine template Parameter Local File Inclusion Vulnerability
390047 – ISPConfig go_info[server][classes_root] File Inclusion
390048 – ManageEngine OpManager searchTerm Cross-Site Scripting
390049 – AliPAGER ubild Cross-Site Scripting and SQL Injection
390050 – MxBB Portal pafileDB Module module_root_path File Inclusion
390051 – Jadu CMS register.php Cross-Site Scripting Vulnerabilities
390052 – OpenFAQ q Parameter Script Insertion Vulnerability
390053 – phpBB foing Module phpbb_root_path File Inclusion
390054 – Sugar Suite sugarEntry Parameter Security Bypass
390055 – Sugar Suite sugarEntry Parameter Security Bypass
390056 – Sugar Suite sugarEntry Parameter Security Bypass
390057 – Sugar Suite exploit
390058 – TikiWiki Multiple Cross-Site Scripting Vulnerabilities
390059 – TikiWiki Multiple Cross-Site Scripting Vulnerabilities
390060 – TikiWiki Multiple Cross-Site Scripting Vulnerabilities
390061 – TikiWiki Multiple Cross-Site Scripting Vulnerabilities
390062 – TikiWiki Multiple Cross-Site Scripting Vulnerabilities
390063 – TikiWiki Multiple Cross-Site Scripting Vulnerabilities
390095 – TikiWiki Multiple Cross-Site Scripting Vulnerabilities
390064 – WordPress shell injection Vulnerability
390065 – Nucleus arbitrary remote inclusion exploit
390066 – Horde passthru exploit
390067 – CMS-Bandits spaw_root File Inclusion Vulnerability
390068 – phpBB Blend Portal System Module phpbb_root_path File Inclusion
390069 – Admanager Pro exploit
390071 – Bible Portal Project destination File Inclusion Vulnerability
390072 – Flipper Poll root_path File Inclusion Vulnerability
390073 – PictureDis Products lang Parameter File Inclusion Vulnerability
390074 – Joomla/Mambo Weblinks blind SQL injection
390076 – Generic m2f_root_path File Inclusion Vulnerability
390077 – Generic PHP download incddir File Inclusion Vulnerability
390078 – SiteDepth CMS SD_DIR Parameter Handling Remote File Inclusion Vulnerability
390079 – PhpLinkExchange page Parameter Handling Remote File Inclusion Vulnerability
390080 – Tests For Valid X-Forwarded Header

recons.conf

350001 – Recons Default Action
350000 – Gravity Board Google Recon attempt
350001 – SilverNews Google Recon attempt
350002 – PHPBB 2.0 Google Recon attempt
350003 – PHPFreeNews Google Recon attempt
350004 – /cgi-bin/guery Google Recon attempt
350005 – tiki-edit Google Recon attempt
350006 – wps_shop.cgi Google Recon attempt
350007 – edit_blog.php Google Recon attempt
350008 – passwd.txt Google Recon attempt
350008 – admin.mdb Google Recon attempt

rootkits.conf

390143 – Root Kits Default Action
390144 – Generic Attempt to install rootkit in Horde
390145 – Generic Attempt to install rootkit

rules.conf

340001 – Got Root Rules Default Action
340000 – Enforce proper HTTP requests
340002 – Generic rule for allowed characters
340004 – Dis-allowed Transfer Encoding
340007 – deny TRACE method
300002 – XSS insertion into headers
300003 – Don’t accept chunked encodings
330003 – Code injection via content length
300004 – generic recursion signatures
300005 – generic recursion signatures
300006 – generic bogus path sigs
330001 – Generic PHP exploit signatures
330002 – Generic PHP exploit signatures
300008 – Generic PHP exploit pattern
300010 – generic XSS PHP attack types
300011 – Prevent SQL injection in cookies
300012 – Prevent SQL injection in UA
300013 – Generic filter to prevent SQL injection attacks
300014 – Generic SQL sigs
300015 – Generic SQL sigs
300016 – Generic SQL sigs
380015 – Meta character SQL injection
300017 – Generic command line attack filter
300018 – Generic PHP code injection protection via ARGS
300040 – Generic PHP code injection protection in URI

useragents.conf

380001 – User Agents Default Action
380000 – Addresses With No HTTP_Accept

————————————————
Ref: http://osdir.com/ml/apache.mod-securityuser/2006-11/msg00148.html

Protected: Vhost entries for svn

October 14, 2007

This content is password protected. To view it please enter your password below:

Clean semaphores owned by nobody

October 14, 2007

for i in `ipcs -s | grep nobody | awk ‘{print $2}’`; do ipcrm -s $i; done

Redirect webmail.domain.com to webmail on a cPanel server

October 14, 2007

Add the following in vhost for webmail.cdomain.com

ProxyPass / http://localhost:2095/
ProxyPassReverse / http://localhost:2095/
ProxyPreserveHost On

Apache 1.3 + mod_ssl + PHP Complile from source – Howto

September 6, 2007

Note : This document comes without warranty of any kind!

Installing Apache web server (1.3.x) with mod_ssl and PHP enabled.
===================================================

1 Get the Source

We need the following software: openssl, apache (1.3.x), mod_ssl and PHP. Down load them to /usr/src

cd /usr/src
wget http://www.openssl.org/source/openssl-0.9.7c.tar.gz
wget http://www.apache.de/dist/httpd/apache_1.3.29.tar.gz
wget http://www.modssl.org/source/mod_ssl-2.8.16-1.3.29.tar.gz

Now go to http://www.php.net and download the latest PHP version to the same loacation.

2 Install Openssl

tar xvfz openssl-0.9.7c.tar.gz
cd openssl-0.9.7c
./config
make
make install

3 Configure and Install mod_ssl and apache

cd /usr/src
tar xvfz apache_1.3.29.tar.gz
tar xvfz mod_ssl-2.8.16-1.3.29.tar.gz
cd mod_ssl-2.8.16-1.3.29
./configure --with-apache=../apache_1.3.29 --with-ssl=/usr/local/ssl/ --prefix=/usr/local/apache --enable-module=most --enable-shared=max --logfiledir=/var/log/httpd --htdocsdir=/usr/local/httpd/htdocs --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc/httpd

(The option –htdocsdir=/usr/local/httpd/htdocs specifies the the default location for documents that will be delivered by this web server is in /usr/local/httpd/htdocs.

Note: You can change the configure command to suit to your needs. Type

./configure --help

to get a list of all configuration options available!)

cd ../apache_1.3.29
make
make certificate TYPE=custom

<- Signature Algorithm: R
<- Country Name: Type your country’s name (e.g DE for Germany)
<- State or Province Name: e.g. Lower Saxony, California, etc.
<- Locality Name: e.g. Lueneburg, Los Angeles, Paris, London, etc.
<- Organization Name: e.g. the name of your company
<- Organizational Unit Name: e.g. IT Department
<- Common Name: e.g. My Company CA
<- Email Address: e.g. info@mycompany.tld
<- Certificate Validity: e.g. 365 (one year)
<- Certificate Version: 3
<- Country Name: see above
<- State or Province Name: see above
<- Locality Name: see above
<- Organization Name: see above
<- Organizational Unit Name: see above
<- Common Name: the fully qualified domain name (FQDN) of your server, e.g. http://www.example.com
<- Email Address: see above
<- Certificate Validity: see above
<- Certificate Version: 3
<- Encrypt the private key now? n
<- Encrypt the private key now? n

(Please note: It is safe to accept the default values for all the questions above because in either case you will receive a warning in your browser if you try to access an SSL site on your server:

If you do not want to get this warning you will have to get a “real” SSL certificate (but this is not for free!). Have a look at the following sites:

* http://www.instantssl.com/ (I would recommend this one.)
* http://www.verisign.com/
* http://www.thawte.com/
* http://www.baltimore.com/
* http://www.ipsca.com/
* http://www.entrust.com/
* http://www.geotrust.com/ )

make install

4 Install PHP

cd /usr/src
tar xvfz php-4.3.4.tar.gz
cd php-4.3.4
./configure --with-apxs=/usr/sbin/apxs --enable-track-vars --enable-sockets --with-config-file-path=/etc --enable-ftp --with-zlib --with-openssl=/usr/local/ssl --enable-force-cgi-redirect --enable-exif --with-gd

(Please note: You can change the configure command to suit to your needs. Type

./configure --help

to get a list of all configuration options available! If you do not specify the –with-mysql[=DIR] option, the bundled MySQL library will be used. This works in most cases.

If you use –with-gd, and you get an error message because of a missing libpng library, install it and then re-run the configure command. On Debian,

If you are on RHEL, uptodate –install libpng-dev libpng2 libpng2-dev libpng3

worked fine for me to install libpng.You can also use http://www.rpmfind.net to find an rpm for you, or have a look at http://www.libpng.org/pub/png/libpng.html.)

make
make install

This will install a PHP binary (normally under /usr/local/bin/php) that can be run from the command line as well as an Apache module.

Now we have to create /etc/php.ini. The easiest way is to take the one that comes with the PHP sources:

cp /tmp/php-4.3.4/php.ini-dist /etc/php.ini

If you like you can now modify /etc/php.ini to suit to your needs.

5 Configure Apache

Now we have to add the following entry in /etc/httpd/httpd.conf (in the section where document types are handled; there should be entries like AddHandler or AddType):

AddType application/x-httpd-php .php .php4 .php3

Create /etc/init.d/httpd:

#!/bin/sh

case "$1" in
start)
/usr/sbin/apachectl startssl
;;
stop)
/usr/sbin/apachectl stop
;;
restart)
$0 stop && sleep 3
$0 start
;;
reload)
$0 stop
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart|reload}"
exit 1
esac

chmod 755 /etc/init.d/httpd

Then start your Apache:

/etc/init.d/httpd start

6 Test your Configuration

netstat -tuap

should show you that Apache uses the ports 80 (http) and 443 (https).

Now go to /usr/local/httpd/htdocs and create a file called info.php with the following contents:

Try to access it with your browser (e.g. using the IP address of the server) via http (e.g. http://192.168.0.1/info.php) and https (https://192.168.0.1/info.php). The output should look similar to this screenshot:

Links

OpenSSL: http://www.openssl.org/
Apache: http://www.apache.org/
mod_ssl: http://www.modssl.org/
PHP: http://www.php.net/
http://www.howtoforge.com/howto_apache_mod_ssl_php4

mod_evasive

September 4, 2007

Mod_evasive is an evasive maneuvers module for Apache to provide evasive
action in the event of an HTTP DoS or DDoS attack or brute force attack. It
is also designed to be a detection tool, and can be easily configured to talk
to ipchains, firewalls, routers, and etcetera.

Detection is performed by creating an internal dynamic hash table of IP
Addresses and URIs, and denying any single IP address from any of the following:

– Requesting the same page more than a few times per second
– Making more than 50 concurrent requests on the same child per second
– Making any requests while temporarily blacklisted (on a blocking list)

This method has worked well in both single-server script attacks as well
as distributed attacks, but just like other evasive tools, is only as
useful to the point of bandwidth and processor consumption (e.g. the
amount of bandwidth and processor required to receive/process/respond
to invalid requests), which is why it’s a good idea to integrate this
with your firewalls and routers.

This module instantiates for each listener individually, and therefore has
a built-in cleanup mechanism and scaling capabilities. Because of this,
legitimate requests are rarely ever compromised, only legitimate attacks. Even
a user repeatedly clicking on ‘reload’ should not be affected unless they do
it maliciously.

———————————————————————————

HOW IT WORKS

A web hit request comes in. The following steps take place:

– The IP address of the requestor is looked up on the temporary blacklist
– The IP address of the requestor and the URI are both hashed into a “key”.
A lookup is performed in the listener’s internal hash table to determine
if the same host has requested this page more than once within the past
1 second.
– The IP address of the requestor is hashed into a “key”.
A lookup is performed in the listerner’s internal hash table to determine
if the same host has requested more than 50 objects within the past
second (from the same child).

If any of the above are true, a 403 response is sent. This conserves
bandwidth and system resources in the event of a DoS attack. Additionally,
a system command and/or an email notification can also be triggered to block
all the originating addresses of a DDoS attack.

=====

HOW TO INSTALL

APACHE v1.3
———————————————————————————

Without DSO Support:

1. Extract this archive into src/modules in the Apache source tree

2. Run ./configure –add-module=src/modules/evasive/mod_evasive.c

3. make, install

4. Restart Apache

With DSO Support, Ensim, or CPanel:

1. $APACHE_ROOT/bin/apxs -iac mod_evasive.c

2. Restart Apache

===============

CONFIGURATION

mod_evasive has default options configured, but you may also add the
following block to your httpd.conf:

APACHE v1.3
———–

DOSHashTableSize 3097
DOSPageCount 2
DOSSiteCount 50
DOSPageInterval 1
DOSSiteInterval 1
DOSBlockingPeriod 10

APACHE v2.0
———–

DOSHashTableSize 3097
DOSPageCount 2
DOSSiteCount 50
DOSPageInterval 1
DOSSiteInterval 1
DOSBlockingPeriod 10

Optionally you can also add the following directives:

DOSEmailNotify you@yourdomain.com
DOSSystemCommand “su – someuser -c ‘/sbin/… %s …'”
DOSLogDir “/var/lock/mod_evasive”

You will also need to add this line if you are building with dynamic support:

APACHE v1.3
———–

AddModule mod_evasive.c

APACHE v2.0
———–

LoadModule evasive20_module modules/mod_evasive20.so

(This line is already added to your configuration by apxs)

DOSHashTableSize
—————-

The hash table size defines the number of top-level nodes for each child’s
hash table. Increasing this number will provide faster performance by
decreasing the number of iterations required to get to the record, but
consume more memory for table space. You should increase this if you have
a busy web server. The value you specify will automatically be tiered up to
the next prime number in the primes list (see mod_evasive.c for a list
of primes used).

DOSPageCount
————

This is the threshhold for the number of requests for the same page (or URI)
per page interval. Once the threshhold for that interval has been exceeded,
the IP address of the client will be added to the blocking list.

DOSSiteCount
————

This is the threshhold for the total number of requests for any object by
the same client on the same listener per site interval. Once the threshhold
for that interval has been exceeded, the IP address of the client will be added
to the blocking list.

DOSPageInterval
—————

The interval for the page count threshhold; defaults to 1 second intervals.

DOSSiteInterval
—————

The interval for the site count threshhold; defaults to 1 second intervals.

DOSBlockingPeriod
—————–

The blocking period is the amount of time (in seconds) that a client will be
blocked for if they are added to the blocking list. During this time, all
subsequent requests from the client will result in a 403 (Forbidden) and
the timer being reset (e.g. another 10 seconds). Since the timer is reset
for every subsequent request, it is not necessary to have a long blocking
period; in the event of a DoS attack, this timer will keep getting reset.

DOSEmailNotify
————–

If this value is set, an email will be sent to the address specified
whenever an IP address becomes blacklisted. A locking mechanism using /tmp
prevents continuous emails from being sent.

NOTE: Be sure MAILER is set correctly in mod_evasive.c
(or mod_evasive20.c). The default is “/bin/mail -t %s” where %s is
used to denote the destination email address set in the configuration.
If you are running on linux or some other operating system with a
different type of mailer, you’ll need to change this.

DOSSystemCommand
—————-

If this value is set, the system command specified will be executed
whenever an IP address becomes blacklisted. This is designed to enable
system calls to ip filter or other tools. A locking mechanism using /tmp
prevents continuous system calls. Use %s to denote the IP address of the
blacklisted IP.

DOSLogDir
———

Choose an alternative temp directory

By default “/tmp” will be used for locking mechanism, which opens some
security issues if your system is open to shell users.

http://security.lss.hr/index.php?page=details&ID=LSS-2005-01-01

In the event you have nonprivileged shell users, you’ll want to create a
directory writable only to the user Apache is running as (usually root),
then set this in your httpd.conf.
WHITELISTING IP ADDRESSES

IP addresses of trusted clients can be whitelisted to insure they are never
denied. The purpose of whitelisting is to protect software, scripts, local
searchbots, or other automated tools from being denied for requesting large
amounts of data from the server. Whitelisting should *not* be used to add
customer lists or anything of the sort, as this will open the server to abuse.
This module is very difficult to trigger without performing some type of
malicious attack, and for that reason it is more appropriate to allow the
module to decide on its own whether or not an individual customer should be
blocked.

To whitelist an address (or range) add an entry to the Apache configuration
in the following fashion:

DOSWhitelist 127.0.0.1
DOSWhitelist 127.0.0.*

Wildcards can be used on up to the last 3 octets if necessary. Multiple
DOSWhitelist commands may be used in the configuration.

TWEAKING APACHE

The keep-alive settings for your children should be reasonable enough to
keep each child up long enough to resist a DOS attack (or at least part of
one). Remember, it is the child processes that maintain their own internal
IP address tables, and so when one exits, so does all of the IP information it
had. For every child that exits, another 5-10 copies of the page may get
through before putting the attacker back into ‘403 Land’. With this said,
you should have a very high MaxRequestsPerChild, but not unlimited as this
will prevent cleanup.

You’ll want to have a MaxRequestsPerChild set to a non-zero value, as
DosEvasive cleans up its internal hashes only on exit. The default
MaxRequestsPerChild is usually 10000. This should suffice in only allowing
a few requests per 10000 per child through in the event of an attack (although
if you use DOSSystemCommand to firewall the IP address, a hole will no
longer be open in between child cycles).

TESTING

Want to make sure it’s working? Run test.pl, and view the response codes.
It’s best to run it several times on the same machine as the web server until
you get 403 Forbidden messages. Some larger servers with high child counts
may require more of a beating than smaller servers before blacklisting
addresses.

Please don’t use this script to DoS others without their permission.

KNOWN BUGS

– This module appears to conflict with the Microsoft Frontpage Extensions.
Frontpage sucks anyway, so if you’re using Frontpage I assume you’re asking
for problems, and not really interested in conserving server resources anyway.

Installing subversion with apache support.

September 4, 2007

wget http://subversion.tigris.org/downloads/subversion-1.4.3.tar.gz
wget http://subversion.tigris.org/downloads/subversion-deps-1.4.3.tar.gz
tar xzvf subversion-1.4.3.tar.gz
tar xzvf subversion-deps-1.4.3.tar.gz
cd subversion-1.4.3
make clean
make clean-swig-py
./configure –with-apxs=/usr/local/apache/bin/apxs –with-apr=/usr/local/apache/bin/apr-1-config –with-apr-util=/usr/local/apache/bin/apu-1-config –with-ssl –with-swig=/usr/local/bin/swig –enable-swig-bindings=python –with-neon=/usr/local
make
make swig-py
make install
make install-swig-py