Bug#706662: siege: coding error can lead to connections going to localhost rather than desired system

On Tue, May 07, 2013 at 09:01:25AM +1200, Michael Hudson-Doyle wrote: Michael Hudson-Doyle michael.hud...@canonical.com writes: Josue Abarca jmasli...@debian.org.gt writes: Hello Michael, thanks for reporting the problem, please, if possible, let me now if you get an answer from

Bug#706662: siege: coding error can lead to connections going to localhost rather than desired system

Michael Hudson-Doyle michael.hud...@canonical.com writes: Josue Abarca jmasli...@debian.org.gt writes: Hello Michael, thanks for reporting the problem, please, if possible, let me now if you get an answer from upstream (He is usually very responsive). I got an answer indeed, and sent him

Bug#706662: siege: coding error can lead to connections going to localhost rather than desired system

Josue Abarca jmasli...@debian.org.gt writes: Hello Michael, thanks for reporting the problem, please, if possible, let me now if you get an answer from upstream (He is usually very responsive). I got an answer indeed, and sent him the attached patch. I can't find a public bug tracker or

Bug#706662: siege: coding error can lead to connections going to localhost rather than desired system

On Fri, May 03, 2013 at 03:23:11PM +1200, Michael Hudson-Doyle wrote: Package: siege Version: 2.70-4 Severity: important Tags: upstream Dear Maintainer, This bug is still in the upstream 3.0.0 release. This code from newsocket in sock.c: int herrno; struct sockaddr_in cli;

Bug#706662: siege: coding error can lead to connections going to localhost rather than desired system

Package: siege Version: 2.70-4 Severity: important Tags: upstream Dear Maintainer, This bug is still in the upstream 3.0.0 release. This code from newsocket in sock.c: int herrno; struct sockaddr_in cli; struct hostent *hp; ... { struct hostent hent; char hbf[8192];