From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat,  4 Jan 2014 07:25:15 -0500
To: 9fans@9fans.net
Message-ID: <da2538d6266b287fc6a9103d5045be4e@brasstown.quanstro.net>
In-Reply-To: <CAL6pNZ-5j9u06B+DMBoxVbtAc7RP-Rv__vzAcVFbHjZPmconYA@mail.gmail.com>
References: <CAL6pNZ83J1L_gLV7qeDyNE44dn04En84DMcF=bR4LLrGOVUc=Q@mail.gmail.com>
	<92045f7f5f2584c96bee474474c3f953@brasstown.quanstro.net>
	<CAL6pNZ-5j9u06B+DMBoxVbtAc7RP-Rv__vzAcVFbHjZPmconYA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] ssh: non standard port
Topicbox-Message-UUID: ac8bad48-ead8-11e9-9d60-3106f5b1d025

> and what client erik?
>
> emi
>
>
> On Sat, Jan 4, 2014 at 11:49 AM, erik quanstrom <quanstro@quanstro.net>wrote:
>
> > On Sat Jan  4 06:44:22 EST 2014, conor.williams@gmail.com wrote:
> >
> > > the ssh client uses port 22...
> > > I want to use port 1700...
> > >
> > > is there a flag?
> >
> > no.  use a normal plan 9 network address, such as
> >         ssh!example.com!1000
> > i tested this with ssh2, but it should work with ssh1
> > as well, but i think in that case the address would
> > be tcp!example.com!1000.

uh, ssh.  as in /$objtype/bin/ssh.  if you get funny results,
i wasn't able to check with a non-standard port, but the
code appears to be there for that.  also, if 9front only has
ssh1, iirc.

- erik