9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: Posix implementation of Plan 9 cpu(1) (Was: [9fans] Command to set samterm label)
Date: Wed, 21 Jul 2021 13:16:07 -0400	[thread overview]
Message-ID: <CAEoi9W4whB=Ty85i2kzJp_d_ZhD7+pOv_yrzdofpxvrQpK99Lw@mail.gmail.com> (raw)
In-Reply-To: <F5E0F844-02B2-46D1-B44B-6E69E39FEB89@gmail.com>

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

On Wed, Jul 21, 2021 at 1:09 PM Xiao-Yong Jin <meta.jxy@gmail.com> wrote:

> > On Jul 21, 2021, at 11:42 AM, Dan Cross <crossd@gmail.com> wrote:
> >
> > On Wed, Jul 21, 2021 at 12:17 PM Xiao-Yong Jin <meta.jxy@gmail.com>
> wrote:
> > > On Jul 21, 2021, at 11:08 AM, Dan Cross <crossd@gmail.com> wrote:
> > > > ssh linuxpc drawterm -c srvdev.rc
> > > >
> > > > yes it's a lot of back and forth, but ssh only is needed for running
> > > > the process, the data afterwards can use 9p directly.
> > >
> > > What's the difference between that and using something like u9fs?
> >
> > auth?
> >
> > This is using ssh to attach to the Linux machine to import it's
> filesystem into the plan9 namespace? Wouldn't authenticating from plan9 to
> Linux over SSH be independent of drawterm vs u9fs?
>
> Drawterm does the proper auth and connect to the plan9 system.
> U9fs needs plan9 srv to auth and connect to it.
>
> If you are running a plan9 system, you probably have your auth
> setup.  If you have access to a posix system, you probably have ssh
> setup and you have access as a normal user, and that enables you
> to do ssh and drawterm back.  No additional setup required.
>
> U9fs, on the contrary, states
>
>           It is typically invoked on a Unix machine by
>           inetd with its standard input and output connected to a net-
>           work connection, typically TCP on an Ethernet.  It typically
>           runs as user root and multiplexes access to multiple Plan 9
>           clients over the single wire.  It assumes Plan 9 uids match
>           Unix login names, and changes to the corresponding Unix
>           effective uid when processing requests.
>
> I'm not going to run this and listen on a public interface even if
> it does not run as root.
>
> There are issues with the auth method that u9fs uses, which I'm not
> going to discuss here.


Nothing prevents you from invoking u9fs over an SSH connection; one needn't
run it from inetd, and I doubt anyone has in 20 years.

        - Dan C.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T09fcdec9c87bfde4-M19bbcae898047761677de240
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

  reply	other threads:[~2021-07-21 17:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  4:52 Lucio De Re
2021-07-19  5:20 ` Michael Misch
2021-07-19  7:13   ` Steve Simon
2021-07-21  3:52     ` Lucio De Re
2021-07-21 14:59       ` Xiao-Yong Jin
2021-07-21 15:11         ` hiro
2021-07-21 16:08           ` Dan Cross
2021-07-21 16:16             ` Xiao-Yong Jin
2021-07-21 16:42               ` Dan Cross
2021-07-21 17:08                 ` Xiao-Yong Jin
2021-07-21 17:16                   ` Dan Cross [this message]
2021-07-21 17:31                     ` Xiao-Yong Jin
2021-07-21 17:57                       ` Dan Cross
2021-07-21 18:09                         ` hiro
2021-07-21 18:11                           ` hiro
2021-07-21 21:41                             ` Steve Simon
2021-07-21 17:41                 ` hiro

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='CAEoi9W4whB=Ty85i2kzJp_d_ZhD7+pOv_yrzdofpxvrQpK99Lw@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=9fans@9fans.net \
    /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).