From owner-freebsd-security@FreeBSD.ORG Wed Sep 17 01:25:05 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D67616A4BF for ; Wed, 17 Sep 2003 01:25:05 -0700 (PDT) Received: from pd2mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8634443FE1 for ; Wed, 17 Sep 2003 01:25:03 -0700 (PDT) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from pd2mr4so.prod.shaw.ca (pd2mr4so-ser.prod.shaw.ca [10.0.141.107])2003))freebsd-security@freebsd.org; Wed, 17 Sep 2003 02:25:02 -0600 (MDT) Received: from pn2ml4so.prod.shaw.ca (pn2ml4so-qfe0.prod.shaw.ca [10.0.121.148]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) freebsd-security@freebsd.org; Wed, 17 Sep 2003 02:25:02 -0600 (MDT) Received: from piii600.wadham.ox.ac.uk (h24-87-233-42.vc.shawcable.net [24.87.233.42])2003)) freebsd-security@freebsd.org; Wed, 17 Sep 2003 02:25:02 -0600 (MDT) Date: Wed, 17 Sep 2003 01:25:00 -0700 From: Colin Percival In-reply-to: <20030917121337.35ebf2c3.tarkhil@webmail.sub.ru> X-Sender: cperciva@popserver.sfu.ca To: Alex Povolotsky Message-id: <5.0.2.1.1.20030917011802.02df0c68@popserver.sfu.ca> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: <20030917063450.GA14894@rot13.obsecurity.org> <20030916210328.U442@ike.othius.com> <20030917063450.GA14894@rot13.obsecurity.org> cc: freebsd-security@freebsd.org Subject: Re: OpenSSH 3.7.1 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 08:25:05 -0000 At 12:13 17/09/2003 +0400, Alex Povolotsky wrote: >I just wonder if recent patches brings openssh from FreeBSD to 3.7 or to >3.7.1 level of protection? It looks like the 3.7.1 patches are in -CURRENT right now, while the release branches and ports only have the 3.7 fix. I think we can safely assume that the security officer will MFC these patches and send out a revised advisory once he is satisfied with them. Colin Percival