Bug#974563: Confirm same problem here
I can confirm that we had the same problem here. I downgraded everything until fixed: apt install libcib4=1.1.16-1 libcrmcluster4=1.1.16-1 libcrmcommon3=1.1.16-1 libcrmservice3=1.1.16-1 liblrmd1=1.1.16-1 libpe-rules2=1.1.16-1 libpe-status10=1.1.16-1 libpengine10=1.1.16-1 libstonithd2=1.1.16-1 libtransitioner2=1.1.16-1 pacemaker=1.1.16-1 pacemaker-cli-utils=1.1.16-1 pacemaker-common=1.1.16-1 pacemaker-resource-agents=1.1.16-1
Bug#670643: libapache2-mod-proxy-html: mod_proxy_html fails to load beacause libxml2.so.2 location is changed.
mod_proxy_html is now part of apache 2.4. This last one is in experimental and will hit unstable soon. mod_proxy_html package is going to be converted to an empty transitional package, hence I'm not going to fix this issue ;) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670633: Processed: found 670633 mod-proxy-html/3.0.1-1
mod_proxy_html is now included in apache 2.4 which is in experimental and will be soon in unstable. mod_proxy_html is going to be replaced by a transitional empty package, hence I won't fix this issue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#475431: Problem with upgrade
On Mon, Apr 21, 2008 at 12:06:21PM +0200, Yves Tan wrote: > Hello, > Hi, > I've the same problem that's Marco De Santis on Debian Etch ! > > I'm hosting websites like this : > > /var/www -> user:www-data group:www-data > /var/www/exemple.tld/www -> user:my_user group:my_usergroup > With the new checks introduced with the security fix (sorry I didn't discovered it when releasing :(), all parents dir must be owned by root or by the user, not another user. So just do a chown root:root /var/www and it should works. It's not a good idea to make the user/group you're http server runs as, own /var/www. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429923: libapache-mod-suphp: Inserting suphp in modules.conf causes memory errors
On Thu, Jun 21, 2007 at 12:52:40PM +0200, Robin Edgar wrote: > Package: libapache-mod-suphp > Version: 0.6.2-1 > Severity: grave > Justification: renders package unusable > > When changing /etc/apache/modules.conf to have both the php5 module AND suphp > loaded (the following 2 lines in /etc/apache/modules.conf: > LoadModule php5_module /usr/lib/apache/1.3/libphp5.so > Loadmodule suphp_module /usr/lib/apache/1.3/mod_suphp.so) > > , the apache errorlog displays the following errors: > First, I'm really sorry for this "late" answer :( I tried to reproduce you're problem but was unable with a clean etch installation, if you already have this problem, can you give me more information on your apache configuration, in particular AddType and hors AddHandler settings. If possible, a tarball of /etc/apache without sensitive informations would be nice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#416424: Bug#415254: SuPHP security issue: using AddHandler instead of AddType]
Same answer as #415254: According to a mail from Jochen Schalanda on the suphp mailing lists. It is not a bug in suphp. It's an apache misconfiguration. He gave us some interesting links: http://httpd.apache.org/docs/2.0/mod/mod_mime.html#multipleext http://httpd.apache.org/docs/1.3/mod/mod_mime.html For people wanting to strictly check the extension, he suggest using SetHandler with FilesMatch. http://httpd.apache.org/docs/2.0/mod/core.html#filesmatch http://httpd.apache.org/docs/2.0/mod/core.html#sethandler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415254: SuPHP security issue: using AddHandler instead of AddType
On Sat, Mar 17, 2007 at 03:22:42PM +0100, Fili wrote: > Package: libapache-mod-suphp > Version: 0.5.2-3 > Severity: critical > > There seems to be a serious security bug when using suphp > with apache 1.3.x on Sarge (and also on Etch). > According to a mail from Jochen Schalanda on the suphp mailing lists. It is not a bug in suphp. It's an apache misconfiguration. He gave us some interesting links: http://httpd.apache.org/docs/2.0/mod/mod_mime.html#multipleext http://httpd.apache.org/docs/1.3/mod/mod_mime.html For people wanting to strictly check the extension, he suggest using SetHandler with FilesMatch. http://httpd.apache.org/docs/2.0/mod/core.html#filesmatch http://httpd.apache.org/docs/2.0/mod/core.html#sethandler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394920: Missed dependancy
On Thu, Oct 26, 2006 at 09:46:54AM +0200, Marco Nenciarini wrote: > package libapache2-mod-proxy-html > severity 394920 grave > thanks > > This module must depends on apache2.2-common to ensure the correct > ABI. > es, I understand, I missed it because apache 2.2 replace apache 2.0 in testing. This is an upgrade issue, I will upload a new version soon with a better Depends. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#297912: mod-proxy-html: FTBFS: syntax error before 'regex_t'
On Thu, Mar 03, 2005 at 04:30:41PM +0100, Andreas Jochens wrote: > Package: mod-proxy-html > Severity: serious > Tags: patch > > +#include > + This fix is incorrect, I'm going to upload a new package with the right fix (use ap_* declarations for regexp). A ll of this is caused by a change in the regexp api between apache 2.0.52 and apache 2.0.53. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#297912: mod-proxy-html: FTBFS: syntax error before 'regex_t'
On Thu, Mar 03, 2005 at 04:01:35PM +0100, Andreas Jochens wrote: > Thank you for your very fast reply! > > I used the following commands on an i386 sid system: > > apt-get source mod-proxy-html > cd mod-proxy-html-2.4.3 > dpkg-buildpackage -b > You're right :) I reproduced this. I think there were some changes in another .h which included this before probably. I will fix this and upload soon. Thanks for the report. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#297912: mod-proxy-html: FTBFS: syntax error before 'regex_t'
On Thu, Mar 03, 2005 at 04:30:41PM +0100, Andreas Jochens wrote: > > When trying to build 'mod-proxy-html', I get the following error: > Could you please tell me more on how you build it (command used) and the architecture used. (because it builds fine on my system and on several architectures by buildd). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#230113: I think this bug can be closed
Package: amavis-ng Version: 0.1.6.9-1 Followup-For: Bug #230113 I checked this bugs. I cannot reproduce it on the bug amavis-ng version (1.6.2) beacause I wasn't able to make it work on unstable ;) But I tried to reproduce it on the latest version without success (in the strace, Fabian Fagerholm seems to did a "MAIL FROM:<..." without space after ":" but in the initial report, this was made by postfix wich I believe doesn't violate rfcs in such way ;) I also found that there is changes related to handling of this "MAIL FROM" address in (old) amavis-ng cvs: http://cvs.sourceforge.net/viewcvs.py/amavis/amavis-ng/AMAVIS/MTA/SMTP.pm?r1=1.23&r2=1.24 So I really think that if the initial author of this bug report doesn't tell us that he as still this bug, we should close it. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-k7 Locale: [EMAIL PROTECTED], LC_CTYPE=fr_FR (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
