From owner-freebsd-security@FreeBSD.ORG Tue Sep 16 11:54:19 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 CCAF516A538 for ; Tue, 16 Sep 2003 11:54:19 -0700 (PDT) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B68E43FBD for ; Tue, 16 Sep 2003 11:54:18 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 4761A54846; Tue, 16 Sep 2003 13:54:18 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id DB6946D454; Tue, 16 Sep 2003 13:54:17 -0500 (CDT) Date: Tue, 16 Sep 2003 13:54:17 -0500 From: "Jacques A. Vidrine" To: Brett Glass Message-ID: <20030916185417.GA6885@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Brett Glass , freebsd-security@FreeBSD.org References: <4.3.2.7.2.20030916123558.02cfdef0@localhost> <20030916134347.GA30359@madman.celabo.org> <4.3.2.7.2.20030916123558.02cfdef0@localhost> <4.3.2.7.2.20030916124550.02a55970@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20030916124550.02a55970@localhost> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-security@FreeBSD.org Subject: Re: OpenSSH heads-up 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: Tue, 16 Sep 2003 18:54:19 -0000 On Tue, Sep 16, 2003 at 12:49:23PM -0600, Brett Glass wrote: > Interesting. > > I could scan the source, but perhaps you already have and can answer > the following questions: > > 1. Could the bug be exploited by someone who had not authenticated > with the server? > > 2. Can it be worked around by changing the configuration until one > has time to patch? (You mention that it's an SSH2 exploit; perhaps > one can disable SSH2 and use SSH1 in the interim?) AFAICT, you need not authenticate, it is not specific to protocol version 2, and there is no workaround. -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se