[9fans] ssh and standalone cpu/auth server?

[9fans] ssh and standalone cpu/auth server?

[rattan]

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

Re: [9fans] ssh and standalone cpu/auth server?

[Devon H. O'Dell]

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

Re: [9fans] ssh and standalone cpu/auth server?

[David Leimbach]

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

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

> 
> 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 ;)
> 
Sure, when do you start? :)


> --Devon
>

Re: [9fans] ssh and standalone cpu/auth server?

[Dave Lukes]

>> 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 ;)
>>
> Sure, when do you start? :)

Give the man a break: he hasn't finished the mozilla port yet.

DaveL

Re: [9fans] ssh and standalone cpu/auth server?

[YAMANASHI Takeshi]

> An ssh out of this server to a remote (Linux box) has
> problems..

The factotum started by the kernel doesn't prompt for keys
on a cpu server.

You might want to start another factotum before ssh.

	cpu% auth/factotum
	cpu% ssh user@remote
--