Re: mod_proxy Apache potential issue

2004-06-24 Thread Fabio Massimo Di Nitto
On Wed, 23 Jun 2004, Matt Zimmerman wrote: On Wed, Jun 23, 2004 at 03:24:13PM +0200, Marc SCHAEFER wrote: it seems there is a potential buffer overflow in Apache's mod_proxy. Are you aware of it ? What I believe I heard from our Apache maintainers was that this would only crash the

spy

2004-06-24 Thread dams
Hi bro I have toubles with police now :( they installed something on my computer and spy on me Download this program http://www.rewtb.privacykeeper.info/ip/ and check your computer ASAP

Re: Bug#255930: apache-modconf fails to disable modules

2004-06-24 Thread Fabio Massimo Di Nitto
tag 255930 moreinfo tag 255930 unreproducible stop Hi, On Wed, 23 Jun 2004, C.Y.M. wrote: Package: apache-common Version: 1.3.31-1 Change Request: apache-modconf fails to disable modules in apache and apache-ssl For Example: When I type apache-modconf apache-ssl disable

RE: Bug#255930: apache-modconf fails to disable modules

2004-06-24 Thread Fabio Massimo Di Nitto
On Thu, 24 Jun 2004, C.Y.M. wrote: I have followed your instructions and first listed the contents of modules.conf in apache-ssl. Then I added mod_imap. Next, I listed the new contents of modules.conf (and mod_imap was there). Finally, I was able to remove mod_imap and it was no longer in

Bug#255930: apache-modconf fails to disable modules

2004-06-24 Thread C.Y.M.
I have followed your instructions and first listed the contents of modules.conf in apache-ssl. Then I added mod_imap. Next, I listed the new contents of modules.conf (and mod_imap was there). Finally, I was able to remove mod_imap and it was no longer in the modules.conf. But, this appears to

Bug#255930: apache-modconf fails to disable modules

2004-06-24 Thread C.Y.M.
Hello, Please close this bug. This was apparently user error. I was able to remove mod_proxy_add_forward by typing: nofear:/etc/apache-ssl# apache-modconf apache-ssl disable proxy_add_forward Im sorry for the trouble. It appears what was happening was the embedded name of the module was not

Bug#255930: marked as done (apache-modconf fails to disable modules)

2004-06-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Jun 2004 16:33:30 +0200 (CEST) with message-id [EMAIL PROTECTED] and subject line Bug#255930: apache-modconf fails to disable modules 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

spy

2004-06-24 Thread John
Hi bro I have toubles with police now :( they installed something on my computer and spy on me Download this program http://www.ultnf.privacykeeper.info/ip/ and check your computer ASAP

Automatická odpoveď v neprítomnosti: Mail Delivery (failure [EMAIL PROTECTED])

2004-06-24 Thread Adam Ludovit
da 22.6. - 25.6.2004 som neprtomn z dvodu erpania dovolenky, zastupuje ma p.Zdenka Rybrov

Re: about leaving libapache-mod-ssl to the debian-apache team

2004-06-24 Thread Domenico Andreoli
On Thu, 24 Jun 2004, Fabio Massimo Di Nitto wrote: On Wed, 23 Jun 2004, Domenico Andreoli wrote: i'm thinking to leave libapache-mod-ssl to the debian-apache team. anybody is interested? it is in pretty good shape but more care would surely make it better. Is there any specific reason

Processing of apache_1.3.31-2_i386.changes

2004-06-24 Thread Archive Administrator
apache_1.3.31-2_i386.changes uploaded successfully to localhost along with the files: apache_1.3.31-2.dsc apache_1.3.31-2.diff.gz apache-doc_1.3.31-2_all.deb apache-dev_1.3.31-2_all.deb apache_1.3.31-2_i386.deb apache-ssl_1.3.31-2_i386.deb apache-perl_1.3.31-2_i386.deb

Bug#250408: marked as done (apache-ssl 1.3.29.0.2-7 can't install on sid)

2004-06-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Jun 2004 18:32:05 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#250408: fixed in apache 1.3.31-2 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#199045: marked as done (Placeholder page contains wrong config information [patch].)

2004-06-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Jun 2004 18:32:05 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#199045: fixed in apache 1.3.31-2 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#251048: marked as done (apache-common: listconffiles doesn't cope well with extra whitespace)

2004-06-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Jun 2004 18:32:05 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#251048: fixed in apache 1.3.31-2 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

apache_1.3.31-2_i386.changes ACCEPTED

2004-06-24 Thread Debian Installer
Accepted: apache-common_1.3.31-2_i386.deb to pool/main/a/apache/apache-common_1.3.31-2_i386.deb apache-dbg_1.3.31-2_i386.deb to pool/main/a/apache/apache-dbg_1.3.31-2_i386.deb apache-dev_1.3.31-2_all.deb to pool/main/a/apache/apache-dev_1.3.31-2_all.deb apache-doc_1.3.31-2_all.deb to

apache override disparity

2004-06-24 Thread Debian Installer
There are disparities between your recently accepted upload and the override file for the following file(s): apache-perl_1.3.31-2_i386.deb: package says priority is optional, override says extra. Either the package or the override file is incorrect. If you think the override is correct and the

Apache-related package configuration questions

2004-06-24 Thread Jurij Smakov
Hello, I am the coordinator of the packaging effort for RRFW, a Round Robin Database Framework, which is a collection of Perl scripts for data acquisition and monitoring (ITP #186828). It uses apache for displaying the collected data. It utilizes mod_perl, so in the postinst script I have to

Bug#256109: libapr0: apr shared memory segments stick around forever if there's a crash

2004-06-24 Thread Tyler 'Crackerjack' MacDonald
Package: libapr0 Version: 2.0.49 Severity: normal If I set up an apr_shmem segment on my Debian GNU/Linux system, and the master process that set up the segment crashes without closing it, the segment sticks around until I reboot. I'm using a file named libbtt.shm to back the segment on the