From owner-freebsd-security  Sat Sep 27 12:30:37 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA08505
          for security-outgoing; Sat, 27 Sep 1997 12:30:37 -0700 (PDT)
Received: from mail.san.rr.com (san.rr.com [204.210.0.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08499
          for <freebsd-security@freebsd.org>; Sat, 27 Sep 1997 12:30:35 -0700 (PDT)
Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97])
	by mail.san.rr.com (8.8.7/8.8.7) with SMTP id MAA01459
	for <freebsd-security@freebsd.org>; Sat, 27 Sep 1997 12:30:04 -0700 (PDT)
Message-Id: <199709271930.MAA01459@mail.san.rr.com>
From: "Studded" <Studded@dal.net>
To: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org>
Date: Sat, 27 Sep 97 12:29:49 -0700
Reply-To: "Studded" <Studded@dal.net>
Priority: Normal
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: samba security fix going into 2.2.5?
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 27 Sep 1997 00:10:20 -0600, Warner Losh wrote:

>I just saw a commit message go by that seemed to be this exact fix.

	Yep... this was confirmed to me in private mail. :)  Thanks to
all those that responded.  And for those keeping score, yes, I did mean
to say "going into the 2.2.5 cd" since samba is not in the base, but is
a port.  I will try to be more clear next time. :)

Doug

Do thou amend thy face,
	and I'll amend my life.
-Shakespeare, "Henry V"