From owner-freebsd-security Mon Oct 4 12:17:24 1999 Delivered-To: freebsd-security@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1DA4B154FB for ; Mon, 4 Oct 1999 12:16:59 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id VAA19882 for freebsd-security@freebsd.org; Mon, 4 Oct 1999 21:16:55 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3B76B87A6; Mon, 4 Oct 1999 20:22:29 +0200 (CEST) Date: Mon, 4 Oct 1999 20:22:29 +0200 From: Ollivier Robert To: freebsd-security@freebsd.org Subject: Re: ssh 1.2.27 vulnerability Message-ID: <19991004202229.A8873@keltia.freenix.fr> Mail-Followup-To: freebsd-security@freebsd.org References: <19991004133635.A13349@shogun.rtsnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991004133635.A13349@shogun.rtsnet.ru> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Igor Vinokurov: > Can someone from FreeBSD Team prove to be true/deny presence > of a problem? And if the problem is - to recommend workaround? AFAIK the problem is on SSH side but a workaround to this problem was committed in FreeBSD recently. Watch the commit logs. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message