Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..

To: Debian User List <debian-user@lists.debian.org>
Subject: Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
Date: Thu, 10 Jul 2008 01:32:07 -0500
Message-id: <[🔎] 4875ACE7.5060701@earthlink.net>
In-reply-to: <[🔎] BAY119-W13BD9384E81D1F65B6EE3FDA910@phx.gbl>
References: <20080710024240.62CF013A695D@liszt.debian.org> <20080710024243.B166913A6968@liszt.debian.org> <[🔎] BAY119-W13BD9384E81D1F65B6EE3FDA910@phx.gbl>

On 07/09/2008 09:52 PM, John Elliot wrote:

Hi,
We have a couple of Sarge servers running bind9(9.2.4-1sarge3) thatappear to be vulnerable to the DNS cache poisoning issue(Looks likeport randomization was only introduced in bind9.3?) - As the serverscannot be upgraded at this time to etch, what is the recommendedcourse of action? Backports and upgrade to 9.3?

There is a version of bind 9.3.4 for Sarge in backports.org, but theydon't publish changelogs, so you'll have to research yourself if thisbug has been fixed in their version.

Reply to:

References:
- Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..
  - From: John Elliot <johnelliot67@hotmail.com>

Prev by Date: OT: Energy efficiency difference btw GNU/Linux, Mac & MS
Next by Date: Re: Missing Edgeport USB driver in recent kernels
Previous by thread: Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..
Next by thread: Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..
Index(es):
- Date
- Thread