From owner-freebsd-security Fri Sep 26 23:10:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA00704 for security-outgoing; Fri, 26 Sep 1997 23:10:26 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA00699 for ; Fri, 26 Sep 1997 23:10:21 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xEq4v-0004CW-00; Sat, 27 Sep 1997 00:10:09 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id AAA28482; Sat, 27 Sep 1997 00:10:20 -0600 (MDT) Message-Id: <199709270610.AAA28482@harmony.village.org> To: cschuber@uumail.gov.bc.ca Subject: Re: samba security fix going into 2.2.5? Cc: "Studded" , "freebsd-security@freebsd.org" In-reply-to: Your message of "Fri, 26 Sep 1997 22:09:58 PDT." <199709270510.WAA07862@cwsys.cwent.com> References: <199709270510.WAA07862@cwsys.cwent.com> Date: Sat, 27 Sep 1997 00:10:20 -0600 From: Warner Losh Sender: owner-freebsd-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199709270510.WAA07862@cwsys.cwent.com> "Cy Schubert - ITSD Open Systems Group" writes: : I'm sure it will. Upgrading the port in the collection is trivial. I just saw a commit message go by that seemed to be this exact fix. Warner