Date: Thu, 24 Jul 2003 17:51:27 -0400 From: Leo Bicknell <bicknell@ufp.org> To: freebsd-hackers@freebsd.org Subject: Re: Network pipes Message-ID: <20030724215127.GA2027@ussenterprise.ufp.org> In-Reply-To: <3F203807.6010805@acm.org> References: <20030724194228.P65000-100000@foem> <3F203807.6010805@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030724215127.GA2027>