Bug#1074912: dircprxy / gcc-14 issue
severity 1074912 important stop Well, when I wrote my message of August 6, I had hoped that someone would actually offer an explanation for why a compiler issue is a dircproxy issue :) I'm not against this being set to serious, but it would be nice if someone could articulate why this is a dircproxy problem when the issue happens with gcc-14, but not with gcc-13. -- Alex Pennace, a...@pennace.org
Bug#1074912: dircproxy build failures
severity 1074912 important stop As far as I can tell, this bug is about a build failure where it builds successfully with a prior version of gcc, but not with a proposed new version. Although that's a concern, I cannot agree that it warrants a serious bug against dircproxy, please correct me if I am wrong. -- Alex Pennace, a...@pennace.org
Bug#477025: libelfg0-dev: Missing on i386
On Sat, Apr 26, 2008 at 04:05:42PM +0200, Josselin Mouette wrote: > libelfg0-dev 0.8.10-1 still includes these headers in /usr/include, > except for the i386 architecture. > > If we have to use the new location, so be it, and I'll happily include > the patch, but the current situation is not acceptable. libelf is in the wrong here, and will be fixed. The build environment for the i386 libelfg0-dev package included et al, which prompted libelf's configure script to not install its own copies. The fix is to force configure to include these compatability headers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445883: CVE-2007-5226 remote denial of service
On Mon, Oct 08, 2007 at 11:55:20PM +0200, Nico Golde wrote: > Hi, > the following CVE (Common Vulnerabilities & Exposures) id was > published for dircproxy. > > CVE-2007-5226[0]: > | irc_server.c in dircproxy 1.2.0 and earlier allows remote attackers to > | cause a denial of service (segmentation fault) via an ACTION command > | without a parameter, which triggers a NULL pointer dereference, as > | demonstrated using a blank /me message from irssi. > > If you fix this vulnerability please also include the CVE id > in your changelog entry. > > The null pointer dereference itself is not that big kind of > a problem here but since this also means to lose the data > you want to read while you are away I mark this as grave. Thanks Nico and Steffen. Security team: this bug is also present in stable and oldstable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#285626: dircproxy: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment
On Thu, Jul 21, 2005 at 10:21:30PM +0100, Roger Leigh wrote: > Unless you plan to make a new upload in the next few days, or have any > objections to the following patch, I intend to NMU dircproxy shortly > to fix this RC bug. The patch is acceptable. Although I do plan to work on dircproxy this weekend, we should bring immediate closure to this FTBFS bug. You can make the NMU at once. Thanks, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
