Bug#130883: (no subject)

2003-12-11 Thread Golden

Processed: Re: Bug#223576: This is a bug in modules-config

2003-12-11 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 223576 important Bug#223576: libapache-mod-python: hangs in modules-config Severity set to `important'. tags 223576 + pending Bug#223576: libapache-mod-python: hangs in modules-config Tags were: sid Tags added: pending merge 223576 221133

Bug#220041: marked as done (modules-update has a will of its own.)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#220041: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#223576: marked as done (libapache-mod-python: hangs in modules-config)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#221138: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#112553: marked as done (More flexible apache configs?)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#192489: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#109460: marked as done (Module headers ought to be installed also (eg: /usr/include/apache-1.3/modules/proxy/mod_proxy.h))

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#109460: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#172527: marked as done (apache-doc: Wrong example for Allow directive)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#172527: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#153528: marked as done (apache: suEXEC can't reopen error log when exec() fails)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#153528: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#89484: marked as done (suEXEC doesn't use PAM sessions to limit processes)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:05 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#89484: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#144644: marked as done (Documentation/comments error on enabling Server-Side Includes (SSI))

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#144644: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#136634: marked as done (apache-ssl: Wrong VirtualHost example)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#136634: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#104268: marked as done (PerlHandler doesn't function in specific circumstance)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#104268: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#170854: marked as done (apache: public_html Directory container should be within IfModule)

2003-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Dec 2003 11:18:04 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#170854: fixed in apache 1.3.29.0.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Re: draft proposal for a new web server policy

2003-12-11 Thread Florian Weimer
Joey Hess wrote: - Any others? In the default configuration, web servers shall bind to localhost only (okay, that's are more general policy issue affecting all network services).

Re: draft proposal for a new web server policy

2003-12-11 Thread Matthew Wilcox
On Thu, Dec 11, 2003 at 07:43:29AM +0100, Florian Weimer wrote: In the default configuration, web servers shall bind to localhost only (okay, that's are more general policy issue affecting all network services). um, that's a completely separate Policy proposal; i don't think it helps anyone to