From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 25 01:39:33 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C8BE37B401 for ; Fri, 25 Jul 2003 01:39:33 -0700 (PDT) Received: from singsing.eng.demon.net (singsing.eng.demon.net [194.217.90.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FE2943FBF for ; Fri, 25 Jul 2003 01:39:32 -0700 (PDT) (envelope-from mike@urgle.com) Received: from michaelb by singsing.eng.demon.net with local (Exim 4.20) id 19fy6t-0004Ld-67; Fri, 25 Jul 2003 09:39:31 +0100 From: Mike Bristow To: Leo Bicknell In-Reply-To: <20030724215127.GA2027@ussenterprise.ufp.org> References: <20030724194228.P65000-100000@foem> <3F203807.6010805@acm.org> <20030724215127.GA2027@ussenterprise.ufp.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: (none) Message-Id: <1059122370.5661.114.camel@singsing.eng.demon.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 25 Jul 2003 08:39:31 +0000 cc: freebsd-hackers@freebsd.org Subject: Re: Network pipes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 08:39:33 -0000 On Thu, 2003-07-24 at 21:51, Leo Bicknell wrote: > In a message written on Thu, Jul 24, 2003 at 12:48:23PM -0700, Tim Kientzle wrote: > > Another approach would be to add a new option to SSH > > so that it could encrypt only the initial authentication, > > then pass data unencrypted after that. This would > > go a long way to addressing the performance concerns. > > ssh -c none? mike@guylian:~$ uname -srm FreeBSD 5.1-RELEASE i386 mike@guylian:~$ ssh -c none localhost No valid ciphers for protocol version 2 given, using defaults. Nice idea. OpenSSH has deliberately broken this, and last time I looked will not entertain unbreaking it. The patch is trivial, though. > Note, you don't want to use password authentication in this case, but > public key should still be ok.