From owner-freebsd-security Thu Aug 27 10:40:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16300 for freebsd-security-outgoing; Thu, 27 Aug 1998 10:40:31 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from burka.rdy.com (burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16182; Thu, 27 Aug 1998 10:39:50 -0700 (PDT) (envelope-from dima@burka.rdy.com) Received: (from dima@localhost) by burka.rdy.com (8.8.8/RDY&DVV) id KAA26294; Thu, 27 Aug 1998 10:38:51 -0700 (PDT) Message-Id: <199808271738.KAA26294@burka.rdy.com> Subject: Re: SSH port In-Reply-To: <19980827092138.B9553@oneinsane.net> from "Ron 'The Insane One' Rosson" at "Aug 27, 1998 9:21:38 am" To: insane@oneinsane.net Date: Thu, 27 Aug 1998 10:38:51 -0700 (PDT) Cc: freebsd-ports@FreeBSD.ORG, freebsd-security@FreeBSD.ORG X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL45 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'll work on this later today. Ron 'The Insane One' Rosson writes: > Is there a reason why we dont have a port of the ver 2.x > ssh. There appears to be an insertion attack in the 1.26 > version that we have in our ports. Sorry for the cross > psot but theis came to my attention from running some tests > on my own machines. > TIA > Ron > -- > -------------------------------------------------------- > Ron Rosson ... and a UNIX user said ... > The InSaNe One rm -rf * > insane@oneinsane.net and all was null and void > -------------------------------------------------------- > It's so nice to be insane, nobody asks you to explain. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message