From owner-freebsd-security Tue May 28 14:53:19 2002 Delivered-To: freebsd-security@freebsd.org Received: from hex.databits.net (hex.csh.rit.edu [129.21.60.134]) by hub.freebsd.org (Postfix) with SMTP id 4CBC837B406 for ; Tue, 28 May 2002 14:53:12 -0700 (PDT) Received: (qmail 98557 invoked by uid 1001); 28 May 2002 21:28:57 -0000 Date: Tue, 28 May 2002 17:28:57 -0400 From: Pete Fritchman To: security@FreeBSD.org, security-officer@FreeBSD.org Subject: Re: FreeBSD Security Notice FreeBSD-SN-02:03 Message-ID: <20020528172857.B88441@databits.net> References: <200205281758.g4SHwHo75682@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200205281758.g4SHwHo75682@freefall.freebsd.org>; from security-advisories@freebsd.org on Tue, May 28, 2002 at 10:58:17AM -0700 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ++ 28/05/02 10:58 -0700 - FreeBSD Security Advisories: | +------------------------------------------------------------------------+ | Port name: ssh2 | Affected: all versions | Status: Not fixed | Password authentication may be used even if password authentication | is disabled. | | +------------------------------------------------------------------------+ FYI, I've just committed an update to the ssh2 port (now at version 3.1.2) which fixes this problem. Thanks to the port maintainer, larse@ISI.EDU, for his quick response. --pete -- Pete Fritchman [petef@(databits.net|freebsd.org|csh.rit.edu)] finger petef@databits.net for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message