On 07/09/2008 09:52 PM, John Elliot wrote:
Hi,
We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that
appear to be vulnerable to the DNS cache poisoning issue(Looks like
port randomization was only introduced in bind9.3?) - As the servers
cannot be upgraded at this time to etch,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Elliot wrote:
Hi,
We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that
appear to be vulnerable to the DNS cache poisoning issue(Looks like port
randomization was only introduced in bind9.3?) - As the servers cannot
be
Hi,
We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that appear to
be vulnerable to the DNS cache poisoning issue(Looks like port randomization
was only introduced in bind9.3?) - As the servers cannot be upgraded at this
time to etch, what is the recommended course of action?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/09/08 21:52, John Elliot wrote:
Hi,
We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that
appear to be vulnerable to the DNS cache poisoning issue(Looks like port
randomization was only introduced in bind9.3?) - As the
4 matches
Mail list logo