* Re: [9fans] ssh and standalone cpu/auth server?
@ 2005-07-13 0:59 YAMANASHI Takeshi
0 siblings, 0 replies; 5+ messages in thread
From: YAMANASHI Takeshi @ 2005-07-13 0:59 UTC (permalink / raw)
To: 9fans
> 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
--
^ permalink raw reply [flat|nested] 5+ messages in thread
* [9fans] ssh and standalone cpu/auth server?
@ 2005-07-12 20:47 rattan
2005-07-12 20:54 ` Devon H. O'Dell
0 siblings, 1 reply; 5+ messages in thread
From: rattan @ 2005-07-12 20:47 UTC (permalink / raw)
To: 9fans
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] ssh and standalone cpu/auth server?
2005-07-12 20:47 rattan
@ 2005-07-12 20:54 ` Devon H. O'Dell
2005-07-14 4:34 ` David Leimbach
0 siblings, 1 reply; 5+ messages in thread
From: Devon H. O'Dell @ 2005-07-12 20:54 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] ssh and standalone cpu/auth server?
2005-07-12 20:54 ` Devon H. O'Dell
@ 2005-07-14 4:34 ` David Leimbach
2005-07-14 5:25 ` Dave Lukes
0 siblings, 1 reply; 5+ messages in thread
From: David Leimbach @ 2005-07-14 4:34 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2005-07-14 5:25 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-07-13 0:59 [9fans] ssh and standalone cpu/auth server? YAMANASHI Takeshi
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 20:47 rattan
2005-07-12 20:54 ` Devon H. O'Dell
2005-07-14 4:34 ` David Leimbach
2005-07-14 5:25 ` Dave Lukes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).