9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] SSHv2
Date: Mon,  2 Apr 2012 19:27:41 -0700	[thread overview]
Message-ID: <3B8AF0D5-DC3F-4012-B2C2-C94ACDC164F6@orthanc.ca> (raw)
In-Reply-To: <eb3e9580c3c35d055165f8b17c1a49df@hamnavoe.com>


On 2012-04-02, at 1:08 PM, Richard Miller wrote:

> I've attempted a minimal conservative addition to standard factotum
> to make it useable with ssh2, and that seems to work for me.  If anyone else
> wants to try it, just replace /sys/src/cmd/auth/factotum/rsa.c with
> /n/sources/contrib/miller/factotum/rsa.c and rebuild.

It's working on my terminal, using both password and rsa auth. I haven't tried genning up a CPU kernel with the new factotum yet.


I notice the new ssh doesn't seem to get along with srv -e.  I tried various permutations of -m, -r, -i, and -I, to no avail (trying to u9fs mount a FreeBSD machine).  It gets as far as starting u9fs, but the communication channel between srv and ssh isn't happy.  In particular, after running

  srv -e 'ssh foo u9fs -na none -u me' foo

the post message appears and the shell prompt comes up, but the underlying ssh still has the terminal window in raw mode. At this point you can type and run blind commands, but any attempts to mount /srv/foo will give you a mount that just generates cloning errors.  I'm guessing ssh might need a flag to force it to do its I/O on fds 0 and 1 rather than /dev/cons ... ?


  reply	other threads:[~2012-04-03  2:27 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  2:10 blstuart
2012-03-30  1:26 ` cinap_lenrek
2012-03-30  3:15   ` Bruce Ellis
2012-03-30  2:14 ` andrey mirtchovski
2012-03-30  4:21 ` Lucio De Re
2012-03-30  4:49 ` Lucio De Re
2012-03-30  6:07   ` David du Colombier
2012-03-30  8:11     ` Lucio De Re
2012-03-30 13:32     ` erik quanstrom
2012-03-30  5:48 ` Jeff Sickel
2012-03-30  8:10 ` steve
2012-03-30  9:19 ` Richard Miller
2012-03-30 10:43   ` Yaroslav
2012-03-30 12:48   ` blstuart
2012-03-30 12:56     ` erik quanstrom
2012-04-02 20:50       ` Richard Miller
2012-04-02 20:08     ` Richard Miller
2012-04-03  2:27       ` Lyndon Nerenberg [this message]
2012-04-03  2:31         ` Lyndon Nerenberg
2012-04-23  8:40       ` rhoyerboat
2012-04-23 20:55         ` Richard Miller
2012-04-25 12:47           ` David Leimbach
2012-04-25 15:25             ` andy zerger
2012-03-30 10:48 ` Yaroslav
2012-03-30 11:00   ` Lucio De Re
2012-03-30 13:03     ` erik quanstrom
2012-03-30 14:19       ` Charles Forsyth
2012-03-30 12:50   ` blstuart
2012-03-30 10:49 ` Yaroslav
2012-03-30 11:17   ` Yaroslav
2012-03-30 13:01     ` blstuart
     [not found] ` <CAG3N4d-1A3VzHsyxSdiRG8-Q9NtYoe8xGUi6B9AVg3inR0Eq_Q@mail.gmail.c>
2012-03-30 12:54   ` erik quanstrom
2012-03-30 13:36 ` erik quanstrom
2012-03-30 13:55   ` Yaroslav
2012-03-30 13:59   ` Lucio De Re
2012-03-30 13:59   ` Lucio De Re
2012-03-30 14:44     ` erik quanstrom
2012-04-02 14:27 ` sl
2012-04-02 14:29   ` erik quanstrom
2012-04-02 14:39     ` erik quanstrom
2012-04-02 16:12   ` Brian L. Stuart
2012-04-02 16:32     ` sl
2012-04-02 16:53       ` sl
2012-04-02 17:21         ` Brian L. Stuart
2012-04-02 17:57           ` sl
2012-04-02 19:52             ` cinap_lenrek
2012-04-02 16:56       ` Brian L. Stuart
2012-04-02 16:27   ` Brian L. Stuart
2012-04-02 16:33     ` sl
2012-04-02 16:44       ` Brian L. Stuart
2012-04-23  1:11 ` andy zerger

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=3B8AF0D5-DC3F-4012-B2C2-C94ACDC164F6@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --cc=9fans@9fans.net \
    /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).