This bug was fixed in the package haproxy - 1.4.24-1
---------------
haproxy (1.4.24-1) unstable; urgency=high
[ Vincent Bernat ]
* New upstream version.
+ CVE-2013-2175: fix a possible crash when using negative header
occurrences.
[ Prach Pongpanich ]
* Drop bashism patch. It seems useless to maintain a patch to convert
example scripts from /bin/bash to /bin/sh.
* Fix reload/restart action of init script (LP: #1187469).
-- Vincent Bernat <[email protected]> Mon, 17 Jun 2013 21:56:26 +0200
** Changed in: haproxy (Ubuntu)
Status: New => Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-2175
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1187469
Title:
haproxy init script gives incorrect exit status
Status in “haproxy” package in Ubuntu:
Fix Released
Bug description:
In /etc/init.d/haproxy, the reload and restart commands always exit
with status 0 (success), even when the haproxy command failed. reload
and restart should be rewritten to follow the pattern of start and
stop, which give informative exit codes.
I'm using ubuntu 12.04, but the problem still appears to exist in
13.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1187469/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
