From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 24 14:51:28 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 BCB1D37B401 for ; Thu, 24 Jul 2003 14:51:28 -0700 (PDT) Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 067B543F85 for ; Thu, 24 Jul 2003 14:51:28 -0700 (PDT) (envelope-from bicknell@ussenterprise.ufp.org) Received: from ussenterprise.ufp.org (bicknell@localhost [127.0.0.1]) by ussenterprise.ufp.org (8.12.9/8.12.9) with ESMTP id h6OLpR8i002127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 24 Jul 2003 17:51:27 -0400 (EDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.12.9/8.12.9/Submit) id h6OLpRfr002126 for freebsd-hackers@freebsd.org; Thu, 24 Jul 2003 17:51:27 -0400 (EDT) Date: Thu, 24 Jul 2003 17:51:27 -0400 From: Leo Bicknell To: freebsd-hackers@freebsd.org Message-ID: <20030724215127.GA2027@ussenterprise.ufp.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20030724194228.P65000-100000@foem> <3F203807.6010805@acm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <3F203807.6010805@acm.org> Organization: United Federation of Planets X-PGP-Key: http://www.ufp.org/~bicknell/ 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: Thu, 24 Jul 2003 21:51:29 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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? Note, you don't want to use password authentication in this case, but public key should still be ok. You could also set up something like kerberos and use krsh or similar... --=20 Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/IFTfNh6mMG5yMTYRAjW1AJ9B9clks7fxIQISByEtGxI2kmpfAwCfQ8F4 RGFzzz5BSrd/jKyH0geqrpA= =m3Fh -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR--