9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] What happened to ssh2?
Date: Tue, 28 Mar 2017 11:11:29 -0400	[thread overview]
Message-ID: <AF04D281-E01C-4701-AF33-8A527ECB7541@stanleylieber.com> (raw)
In-Reply-To: <CAG2UyHpr35pznd9EDbDhn5-04kGt0wYbSUmLDS9n68_WzhNghQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

On Mar 28, 2017, at 10:22 AM, Dave MacFarlane <driusan@gmail.com> wrote:
> 
> I've had some success connecting to modern Linux machines that are
> ssh2-only with github.com/mattn/sshgo, but while looking into if I
> could make it a little smarter about things like getting credentials
> from factotum or stripping \r from the output, I noticed that Plan 9
> already has an ssh2 command which is missing from 9front.
> 
> Why was it removed? Is there an alternative that's already part of the
> base system I could use instead of having to write something?
> 
> - Dave

The ssh2 client that was added to the Labs distribution of Plan 9 (rewritten by Geoff) was never added to 9front because it sucks. The original Coraid version was omitted for the same reason. Recently, the old ssh1 client was also removed.

The best option right now is mischief's scpu:

http://fqa.9front.org/fqa8.html#8.4.6.3

sl


[-- Attachment #2: Type: text/html, Size: 1482 bytes --]

  reply	other threads:[~2017-03-28 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 14:22 Dave MacFarlane
2017-03-28 15:11 ` Stanley Lieber [this message]
2017-03-28 19:03   ` [9front] " Aram Hăvărneanu
2017-03-28 19:05     ` Kurt H Maier
2017-03-28 19:09       ` Aram Hăvărneanu
2017-03-28 19:18         ` Stanley Lieber
2017-03-28 19:34     ` Steve Simon
2019-08-15  7:48 ori
2019-08-15  7:51 ori

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=AF04D281-E01C-4701-AF33-8A527ECB7541@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /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).