From owner-freebsd-security  Fri Feb 16 07:16:00 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA09177
          for security-outgoing; Fri, 16 Feb 1996 07:16:00 -0800 (PST)
Received: from alpha.dsu.edu (ghelmer@alpha.dsu.edu [138.247.32.12])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA09172
          for <freebsd-security@freebsd.org>; Fri, 16 Feb 1996 07:15:55 -0800 (PST)
Received: (from ghelmer@localhost) by alpha.dsu.edu (8.7.3/8.7.3) id JAA07629; Fri, 16 Feb 1996 09:15:54 -0600 (CST)
Date: Fri, 16 Feb 1996 09:15:53 -0600 (CST)
From: Guy Helmer <ghelmer@alpha.dsu.edu>
To: freebsd-security@freebsd.org
Subject: named update
Message-ID: <Pine.OSF.3.91.960216090524.4301D-100000@alpha.dsu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-security@freebsd.org
Precedence: bulk

Does anyone know the named version details surrounding the named problem
that CERT just reported?  I just don't know which version tries to close
up the hole.  Is named in 2.0.5 and 2.1.0 a vulnerable version? 

Thanks to anyone who can shed light on this,
Guy

Guy Helmer, Dakota State University Computing Services - ghelmer@alpha.dsu.edu