From owner-freebsd-security  Tue Nov 19 16:38:55 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA19101
          for security-outgoing; Tue, 19 Nov 1996 16:38:55 -0800 (PST)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA19096
          for <freebsd-security@freebsd.org>; Tue, 19 Nov 1996 16:38:50 -0800 (PST)
Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.8.3/8.8.3) with ESMTP id QAA18266 for <freebsd-security@freebsd.org>; Tue, 19 Nov 1996 16:38:20 -0800 (PST)
Received: (from pst@localhost) by base.jnx.com (8.7.6/8.7.3) id QAA01299; Tue, 19 Nov 1996 16:38:10 -0800 (PST)
From: FreeBSD Security Officer <security-officer@freebsd.org>
cc: freebsd-security@freebsd.org
Subject: Re: Serious BIND resolver problem. (fwd)
References: <Pine.LNX.3.92.961119151129.1956A-100000@super-g.inch.com>
	<Pine.LNX.3.95.961119174603.12421G-100000@dark.sinister.com>
Date: 19 Nov 1996 16:38:09 -0800
In-Reply-To: security@sinister.com's message of 19 Nov 96 22:48:11 GMT
Message-ID: <7ypw19iosu.fsf@base.jnx.com>
Lines: 9
X-Mailer: Gnus v5.2.25/XEmacs 19.14
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


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