From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: Lyndon Nerenberg In-Reply-To: Date: Mon, 2 Apr 2012 19:27:41 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3B8AF0D5-DC3F-4012-B2C2-C94ACDC164F6@orthanc.ca> References: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] SSHv2 Topicbox-Message-UUID: 74e5ef94-ead7-11e9-9d60-3106f5b1d025 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 ... ?=