From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3e1162e605071321341d27cf7b@mail.gmail.com>
Date: Wed, 13 Jul 2005 23:34:09 -0500
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ssh and standalone cpu/auth server?
In-Reply-To: <42D42E20.5060701@offmyserver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <Pine.GSO.4.61.0507121643001.17085@cps210>
	<42D42E20.5060701@offmyserver.com>
Topicbox-Message-UUID: 6693eb46-ead0-11e9-9d60-3106f5b1d025

On 7/12/05, Devon H. O'Dell <dodell@offmyserver.com> wrote:
> rattan wrote:
> >
> > I have a kfs based standalone cpu/auth standalone server.
> >
> > An ssh out of this server to a remote (Linux box) has
> > problems..
> >
> > cpu% ssh user@remote
> > server remote not on key ring.
> > add key to keyfile (a), continue without adding key (b), or exit (s) [e=
]a
> > ssh: client authentication failed.
> > cpu%
> >
> > But if reboot the same box into a terminal ssh out to remote box
> > works (same dialog except the authentication succedes).
> >
> > -ishwar
>=20
> Your Linux machine probably does one of two things (or both):
>=20
> a) disables SSHv1, and / or
> b) requires OPIE / S/Key / similar authentication for SSHv1

He said it works in terminal mode so that's probably got nothing to do with=
 it.

>=20
> The reason for these behaviors is a bug in the SSHv1 protocol. It'd be
> really nice to have an sshv2 client for Plan 9. Hint hint ;)
>=20
Sure, when do you start? :)


> --Devon
>