Multiple regressions in dnsmasq 2.43, merge to 2.45 needed

Bug #250444 reported by Thierry Carrez
2
Affects Status Importance Assigned to Milestone
dnsmasq (Ubuntu)
Fix Released
High
Thierry Carrez

Bug Description

Binary package hint: dnsmasq

Release 2.43 has been merged in intrepid to fix a security issue.
However this release introduces multiple regressions that have been fixed in releases 2.44 and 2.45 :

version 2.44
            Fix crash when unknown client attempts to renew a DHCP
            lease, problem introduced in version 2.43. Thanks to
            Carlos Carvalho for help chasing this down.

     Fix potential crash when a host which doesn't have a lease
     does DHCPINFORM. Again introduced in 2.43. This bug has
     never been reported in the wild.

            Fix crash in netlink code introduced in 2.43. Thanks to
            Jean Wolter for finding this.

version 2.45
            Fix total DNS failure in release 2.43 unless --min-port
            specified. Thanks to Steven Barth and Grant Coady for
            bugreport. Also reject out-of-range port spec, which could
            break things too: suggestion from Gilles Espinasse.

Thierry Carrez (ttx)
Changed in dnsmasq:
assignee: nobody → tcarrez
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
Thierry Carrez (ttx) wrote :

Debdiff for the merge from Debian 2.45-1

Changed in dnsmasq:
importance: Medium → High
status: In Progress → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dnsmasq - 2.45-1ubuntu1

---------------
dnsmasq (2.45-1ubuntu1) intrepid; urgency=low

  * Merge from debian unstable (LP: #250444), remaining changes:
     - TearDown spec recommendations in debian/postinst and debian/init
     - debian/control: Updated maintainer to match DebianMaintainerField

 -- Thierry Carrez <email address hidden> Mon, 21 Jul 2008 09:50:57 +0200

Changed in dnsmasq:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.