From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <42D42E20.5060701@offmyserver.com>
Date: Tue, 12 Jul 2005 13:54:56 -0700
From: "Devon H. O'Dell" <dodell@offmyserver.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404)
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ssh and standalone cpu/auth server?
References: <Pine.GSO.4.61.0507121643001.17085@cps210>
In-Reply-To: <Pine.GSO.4.61.0507121643001.17085@cps210>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 659fc552-ead0-11e9-9d60-3106f5b1d025

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

Your Linux machine probably does one of two things (or both):

a) disables SSHv1, and / or
b) requires OPIE / S/Key / similar authentication for SSHv1

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 ;)

--Devon