Subject: Re: [9front] [PATCH] private /srv attach option
Date: Mon, 30 May 2022 10:56:32 -0400 [thread overview]
Message-ID: <F6E8DFA6B08AF5FBD2A9AAAEBF4A9444@eigenstate.org> (raw)
Quoth Jacob Moody <email@example.com>:
> Attaching a private /srv does not effect future
> attaches to '#s' without the private option.
> I figure the global /srv can be explicitly
> given up through chdev if desired.
also, maybe it's time to sit down and think about
where this all goes, rather than tossing random
diffs over the fence.
- What is the current state of locking down... things?
- Why is the current state insufficient?
- Are there places where the current state should have
been used, but wasn't because of its flaws?
- What exactly is the approach to securing things that
we're trying to approach?
A soup of new features of 'rfork M' quality is a problem;
let's figure out where we're going.
next prev parent reply other threads:[~2022-05-30 14:58 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
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 [this message]
2022-07-10 21:47 ` ori
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 \
* 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).