9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John Floren" <slawmaster@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: ssh2, at long last!
Date: Wed,  2 Jan 2008 16:20:43 -0800	[thread overview]
Message-ID: <7d3530220801021620k74c600efn514ff5e324f736ca@mail.gmail.com> (raw)
In-Reply-To: <7d3530220801021505v32192085p602a8a2c395785fd@mail.gmail.com>

On Jan 2, 2008 3:05 PM, John Floren <slawmaster@gmail.com> wrote:
>
> On Jan 2, 2008 2:29 PM, John Floren <slawmaster@gmail.com> wrote:
> > Okay, we've all been waiting for ssh2 on Plan 9 for quite a few years.
> > Ron Minnich and I have hacked around on Andrey's port of ssh2 to the
> > point where it is moderately usable. The client is extremely basic. It
> > doesn't send anything to the server until you hit enter; don't expect
> > to be using emacs any time soon under this, but you can use your basic
> > commands. It seems to take the whole window with it sometimes upon
> > exit, but we're hoping that by having more people banging on it we can
> > get these things worked out before long.
> > The source is at /n/sources/contrib/john/libssh2.tgz
> > (http://netlib.bell-labs.com/sources/contrib/john/libssh2.tgz);
> > there's also a precompiled binary at /n/sources/contrib/john/ssh2
> > If you want debugging, set the SSH2DEBUG variable to a hex value
> > before running. 0xFF will set maximum debugging, I don't know the
> > other values.
> > Please send feedback; anybody who wants to write a more complex client
> > should do that ASAP.
> >
>
> Stupid mistake on my part... the file I put up as libssh2.tgz is not,
> in fact, a gzipped tarball. It's just a tar. I'm running bzip2 as we
> speak, so you can get libssh2.tbz in a few minutes
>

After an amazingly fast bit of hacking, Aki has given us raw mode, so
you can now run (to a limited extent) vi and stuff like that. Note
that you'll have to set up the terminal type after you log in, using
'export TERM=vt102'.
Oh, and run the client in vt. It'll play nicely with your colors, let
vi work almost properly, and when the client dies at the end, it just
takes out vt, not the window you ran it in.
In my usual crackheaded fashion, I've decided to distribute using .tgz
this time instead of .tbz, since .tgz seems to be more of the standard
and easier to deal with, in my opinion. So we now have an updated
libssh2.tgz and ssh2 binary in contrib/john
Enjoy (thanks Aki!)


John
-- 
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn


  reply	other threads:[~2008-01-03  0:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 22:29 [9fans] " John Floren
2008-01-02 23:05 ` [9fans] " John Floren
2008-01-03  0:20   ` John Floren [this message]
2008-01-03 18:56     ` John Floren
2008-01-03 19:43       ` Charles Forsyth
2008-01-03 21:35         ` ron minnich
2008-01-02 23:13 ` [9fans] " Armando Camarero
2008-01-02 23:48 ` ron minnich
2008-01-03 19:14 [9fans] " marina

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=7d3530220801021620k74c600efn514ff5e324f736ca@mail.gmail.com \
    --to=slawmaster@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).