9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] private /srv attach option
Date: Mon, 30 May 2022 16:04:15 -0400	[thread overview]
Message-ID: <847F45EC7225C1D0B69E796B69D6E3ED@eigenstate.org> (raw)
In-Reply-To: <b3419c6e-04a8-69f0-f7da-badbf0721155@posixcafe.org>

Quoth Jacob Moody <moody@mail.posixcafe.org>:
> > A soup of new features of 'rfork M' quality is a problem;
> > let's figure out where we're going.
> >
> Ouch.
> For the record I did discuss some of these /srv ideas
> in another thread, I believe the it was the one for git/serve to use chdev.
> Nobody seemed interested in discussing it then.

in isolation, this change seems.. fine, I guess. It does
something useful, though it's got some inelegance around
needing a global view to get a clean /srv, which means
that a restricted /srv can't get a clean /srv. It's also
encoded into the interface, so we can't easily fix it

This may or may not matter, I don't know.

the gripe I have is that I know you're aiming turn namespaces
into useful security boundaries, as well as providing other
ways to ratchet down permissions. But I haven't seen a summary
of the changes you feel are needed, the places and ways that
they'd be used, and a diversity of examples that demonstrate
the changes are parsimonious and sufficient.

What is the end goal, and what should it be?

Let's not design in a vaccuum.

  reply	other threads:[~2022-05-30 20:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 11:50 Jacob Moody
2022-05-30 14:44 ` ori
2022-05-30 17:26   ` Jacob Moody
2022-05-30 20:04     ` ori [this message]
2022-05-31  7:03       ` hiro
2022-05-31 15:09         ` Jacob Moody
2022-05-31 16:04           ` Jacob Moody
2022-06-08 14:48             ` Jacob Moody
2022-06-22 15:22               ` cinap_lenrek
2022-05-30 14:56 ` ori
2022-07-10 21:47 ` 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:

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

  git send-email \
    --in-reply-to=847F45EC7225C1D0B69E796B69D6E3ED@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).