From: Cliff Woolley [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 06, 2003 4:40 AM
On Sat, 5 Jul 2003, Joshua Slive wrote:
One possible thing we could do is simply remove the sample proxy config
from our default httpd.conf. These samples make it too easy for people to
activate a proxy
Fun.
- Original Message -
From: Info iNetD [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, July 05, 2003 7:34 PM
Subject: Spam postings via Apache to postfix on the same host
Hello,
Hello,
I have found out on two different machines that somebody is posting spam
to
On Sat, 5 Jul 2003, David Reid wrote:
203.98.177.86 - - [24/Jun/2003:12:33:27 +0200] POST
http://xx.xx.xx.xx:25/ HTTP/1.1 200 208
Yes, it's an apache configuration problem. They set ProxyRequests On
without properly securing their proxy server. This means they can be
abused for tons of
* Joshua Slive wrote:
[spam via proxy]
One possible thing we could do is simply remove the sample proxy config
from our default httpd.conf. These samples make it too easy for people to
activate a proxy without securing it properly.
+1! Since proxying is not the primary purpose of the httpd I
-
From: Joshua Slive [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, July 05, 2003 7:44 PM
Subject: Re: Fw: Spam postings via Apache to postfix on the same host
On Sat, 5 Jul 2003, David Reid wrote:
203.98.177.86 - - [24/Jun/2003:12:33:27 +0200] POST
http://xx.xx.xx.xx:25
André Malo [mailto:[EMAIL PROTECTED] wrote:
* Joshua Slive wrote:
[spam via proxy]
One possible thing we could do is simply remove the sample
proxy config
from our default httpd.conf. These samples make it too
easy for people to
activate a proxy without securing it properly.
+1!
On Sat, 5 Jul 2003, Joshua Slive wrote:
One possible thing we could do is simply remove the sample proxy config
from our default httpd.conf. These samples make it too easy for people to
activate a proxy without securing it properly.
+1
--Cliff