From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] SSH server?
Date: Sat, 22 Jan 2022 17:35:36 +0000 [thread overview]
Message-ID: <7679B03A-8181-4178-84E1-947CBF961A08@quintile.net> (raw)
In-Reply-To: <87k0er52bo.fsf@turtle-trading.net>
no probs, just an idea. i only ever used sshd once to prove to myself it works., and that was decades ago (ssh1).
-Steve
On 22 Jan 2022, at 3:57 pm, Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net> wrote:
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
next prev parent reply other threads:[~2022-01-23 2:17 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 [this message]
2022-01-22 18:16 ` 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=7679B03A-8181-4178-84E1-947CBF961A08@quintile.net \
--to=steve@quintile.net \
--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).