Apache 1.3.31

[l0rdphi1]

http://help.directadmin.com/item.php?id=1

That worked great for me, minus this:

[root@server1 admin]# httpd -v
bash: httpd: command not found

Had to do

[root@server1 admin]# /usr/sbin/httpd -v
Server version: Apache/1.3.31 (Unix)
Server built:   May 25 2004 22:22:48

Also none of the handy service commands work:

[root@server1 admin]# service httpd restart
bash: service: command not found

Have to do:

/etc/rc.d/init.d/httpd restart

(however I just noticed

/sbin/service httpd restart

does indeed work.)

I'm on RHEL3.

 

[ProWebUK]

How did you login?

if you used su from admin, make sure you use:

su -

NOT

su

Since both httpd and service commands dont work, it seems your paths are incorrect which is what the above would cause

Chris

 

[l0rdphi1]

WOW! I never would have guessed that the cause..

Good job!

 

[MagnuM]

Commands specified at http://help.directadmin.com/item.php?id=1 worked fine form me. My Apache version is now 1.3.31. Thanks, John.

 

[deltaned]

Apache 1.3.31 is not OK I read at www.webwereld.nl
(sorry dutch)
Apache 1.3.32 is out now include the patch to fix the securety problem.

Is the update here avalible?

 

[jmstacey]

Theres nothing on the apache website about a release

 

[Icheb]

Theres nothing on the apache website about a release

Well let's see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0492
Or http://www.apacheweek.com/issues/04-06-11 for the entire story & information.

quote from apacheweek:[br]CAN-2004-0492: Important flaw in mod_proxy
An important security issue was reported in mod_proxy on the 10th June. The Common Vulnerabilities and Exposures project has assigned the name CAN-2004-0492 to this issue.

The flaw affects Apache httpd versions 1.3.26, 1.3.27, 1.3.28, 1.3.29 and 1.3.31 that have mod_proxy enabled and configured. Apache httpd 2.0 and other versions of Apache httpd 1.3 are unaffected.

In default installs of DA, mod_proxy is disabled as far as i know...
So this wouldn't be dangerous for us.