9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] SSH server?
Date: Sat, 22 Jan 2022 13:16:18 -0500	[thread overview]
Message-ID: <C8C85183FACBC09EE729205078716621@eigenstate.org> (raw)
In-Reply-To: <87k0er52bo.fsf@turtle-trading.net>

Quoth Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>:
> Hi Steve,
> Steve Simon writes:
> > I believe the drawterm that 9front uses can run headless.
> Sure, that is what we currently use as a go-between for SSH.  It had to
> be hacked to better isolate the 9front machine from the rest of the
> network, but that already works.
> > wouldn't this be a better solution (using native plan9 protocols)
> > rather than importing ssh?
> This build farm also serves a number of other systems.  like primarily
> Linux and BSDs.  9front is the one that requires a special setup in the
> framework.  This is implemented, but it's suboptimal and it produces its
> own bugs.  It would be better IMO to handle Plan 9 as any other system.
> That's why I'm asking.  And that's also why suggesting some other tool
> in general is not an answer to my question, sorry :-(.
> Thanks, benny

Yeah. an ssh server would e nice to have (I'd use it to
serve repos for unix access on shithub), but there's no
great one ready to go. The best option mentioned is by

      parent reply	other threads:[~2022-01-23 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 14:36 Benjamin Riefenstahl
2022-01-21 15:04 ` Stanley Lieber
2022-01-21 15:35   ` Benjamin Riefenstahl
2022-01-21 15:18 ` Sigrid Solveig Haflínudóttir
2022-01-22 13:28   ` Benjamin Riefenstahl
2022-01-21 16:23 ` Steve Simon
2022-01-21 21:59   ` Thaddeus Woskowiak
2022-01-22  8:50     ` sirjofri
2022-01-22 13:26   ` Benjamin Riefenstahl
2022-01-22 17:35     ` Steve Simon
2022-01-22 18:16     ` ori [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C8C85183FACBC09EE729205078716621@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \


* 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).