-BEGIN PGP SIGNED MESSAGE-
Joshua Slive [mailto:[EMAIL PROTECTED] wrote:
On Thu, 4 Sep 2003, Jeroen Massar wrote:
Requiring a IKnowIAmOperatingAOpenProxy flag that needs to
be set explicitly would be a better idea then :)
That's what the ProxyRequests directive does. Giving it a
On Tue, 2 Sep 2003, Chris Knight wrote:
Joshua Slive wrote:
I think we've done pretty-much all we can. I wouldn't mind putting a
little note on the httpd.apache.org homepage saying Have you secured your
proxy? and point to the correct docs.
What about sending a warning message to
-BEGIN PGP SIGNED MESSAGE-
Joshua Slive [mailto:[EMAIL PROTECTED] wrote:
I don't think that is feasible. There are MANY ways to do
access control in apache.
Sending a message along the lines of Your server is
configured to proxy requests to arbitrary servers. whenever
On Thu, 4 Sep 2003, Jeroen Massar wrote:
Requiring a IKnowIAmOperatingAOpenProxy flag that needs to
be set explicitly would be a better idea then :)
That's what the ProxyRequests directive does. Giving it a silly name
isn't going to help ;-)
Seriously, we could add a default deny for
At 02:41 PM 9/4/2003, Joshua Slive wrote:
Seriously, we could add a default deny for outgoing port
25 (smtp) and 6660-6670 (irc) proxied connections.
This won't really hurt anyone as I don't see any reasons
why anybody would want that. A special AllowProxyPorts 25 6660-6670
directive could
Joshua Slive wrote:
I think we've done pretty-much all we can. I wouldn't mind putting a
little note on the httpd.apache.org homepage saying Have you secured your
proxy? and point to the correct docs.
What about sending a warning message to stderr/error_log upon startup if
the proxy is not
On Thu, 28 Aug 2003, Eli Marmor wrote:
According to research companies, most of the current spamming is done
using HTTP proxies. Spammers assistant scripts scan the net 24 hours a
day, looking for open proxies, and then use them to spread the spam.
Correct. And people continue to submit this
On Thu, 28 Aug 2003, Eli Marmor wrote:
According to research companies, most of the current spamming is done
using HTTP proxies.
I find that hard to believe. I believe a substantial amount of spam comes
this way, but most seems unlikely.
1. Is there any existing code and/or module that
Problem can come from your module to be linked with external shared
libraries.
Look at:
http://www.megalith.co.uk/manual/dso.html
hope it helps,
cheers,
--jakub
--- In [EMAIL PROTECTED], Cliff Woolley [EMAIL PROTECTED] wrote:
On Thu, 28 Aug 2003, Eli Marmor wrote:
According to research
* szymanski_j wrote:
[smtp over http proxy]
Problem can come from your module to be linked with external shared
libraries.
???
nd
--
Wenn nur Ingenieure mit Diplom programmieren würden, hätten wir
wahrscheinlich weniger schlechte Software.
Wir hätten allerdings auch weniger gute Software.
At 12:23 PM 8/28/2003, André Malo wrote:
* szymanski_j wrote:
[smtp over http proxy]
Problem can come from your module to be linked with external shared
libraries.
???
I could not understand your reference, either. Would you further explain
how DSOs have any relationship with using HTTP
The issue that the reporter, Jason Robertson, suggested to partially solve
this proble is that we should add another AllowConnect directive, such as
AllowHttpProxy, to restrict the ports that you can use to proxy HTTP traffic.
We already have this restriction available for CONNECT (usually https)
On Thu, 28 Aug 2003, Joshua Slive wrote:
I think we've done pretty-much all we can. I wouldn't mind putting a
little note on the httpd.apache.org homepage saying Have you secured your
proxy? and point to the correct docs.
+1.
Additionally, Eli and I have been conversing a bit more off-list,
13 matches
Mail list logo
