Date: Fri, 28 Sep 2001 12:10:13 -0600 From: Nate Williams <nate@yogotech.com> To: John Baldwin <jhb@FreeBSD.org> Cc: Nate Williams <nate@yogotech.com>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Gregory Neil Shapiro <gshapiro@FreeBSD.org>, Josef Karthauser <joe@tao.org.uk> Subject: Re: cvs commit: src/crypto/openssh atomicio.h auth-chall.c auth2 Message-ID: <15284.48389.405358.260088@nomad.yogotech.com> In-Reply-To: <XFMail.010928110814.jhb@FreeBSD.org> References: <15284.47627.949591.179153@nomad.yogotech.com> <XFMail.010928110814.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> > > if you list "Protocol 2", attempts to > >> > > contact a protocol 1 only sshd would fail; > >> > > >> > True, but that's because there is no way to force the client to do a > >> > SSH1 connection. However, the client is capable of supporting ssh v1, > >> > it's just not available to you via the command line. (Note to developers > >> > listening, that would be a good command-line switch to add, like > >> > 'ssh -1'.) > >> > >> Yes it is, it's just a mouthful: > >> > >> % ssh -o 'Protocol 1' hostname > > > > Thanks for the hint. I like 'ssh -1' better, although not so much as to > > implement and submit a patch to the maintainers. :( > > Actually, I use ssh -1 in current all the time. In fact, both ssh -1 > and ssh -2 work in -current. Not sure about stable, but then again, > current's ssh just got MFC'd, so presumably... :) Ahh, maybe when I update my tree I'll get a client that allows it. The one in 4.4-R does not support 'ssh -1'. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15284.48389.405358.260088>