9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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?
Date: Wed, 13 Jul 2005 23:34:09 -0500	[thread overview]
Message-ID: <3e1162e605071321341d27cf7b@mail.gmail.com> (raw)
In-Reply-To: <42D42E20.5060701@offmyserver.com>

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
>


  reply	other threads:[~2005-07-14  4:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 20:47 rattan
2005-07-12 20:54 ` Devon H. O'Dell
2005-07-14  4:34   ` David Leimbach [this message]
2005-07-14  5:25     ` Dave Lukes
2005-07-13  0:59 YAMANASHI Takeshi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e1162e605071321341d27cf7b@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).