Date: Wed, 20 Nov 1996 09:19:40 +0000 From: Tom Fischer <tfischer@panoramix.rain.fr> To: FreeBSD Security Officer <security-officer@freebsd.org> Cc: freebsd-security@freebsd.org Subject: Re: Serious BIND resolver problem. (fwd) Message-ID: <3292CD2C.41C67EA6@panoramix.rain.fr> References: <Pine.LNX.3.92.961119151129.1956A-100000@super-g.inch.com> <Pine.LNX.3.95.961119174603.12421G-100000@dark.sinister.com> <7ypw19iosu.fsf@base.jnx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, "quietly fixed?" I'm not too sure I like the sound of that. I'm running 2.1.0-Release, installed off the January 1996 cdrom on several systems. I'm installed all of the patches, etc., that were available on ftp://freebsd.org/pub/CERT/patches, and I don't remember anything about this problem (apparently, obviously). My question is: Do I need to do something to my libc library? As I understand it, 2.1R from the cd is not the same thing as 2.1 -stable... or am I wrong? thanks, tom tfischer@rain.fr ===================================================== FreeBSD Security Officer wrote: > > The SNI advisory is for a problem that had been corrected quite some time ago. > This is a "late" advisory causing lots of folks confusion. > > The problem is in the resolver libraries (in libc). Upgrading named to 4.9.5 > will not fix this problem. This problem was quietly fixed in 2.1 -stable and > -current releases by explicit request of the author several months ago. > > Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3292CD2C.41C67EA6>