From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sendfd() on native Plan 9?
Date: Sun, 4 Jan 2009 00:58:30 -0500 [thread overview]
Message-ID: <20090104055830.GI8355@masters10.cs.jhu.edu> (raw)
In-Reply-To: <dd19e12ccb2d34fe06ce31e9540a86b2@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]
On Sun, Jan 04, 2009 at 07:19:35AM +0200, lucio@proxima.alt.za wrote:
> > '#p'
> > allows any of my namespaces to debug processess in any other, '#s' is too
> > global, and /net seems to allow any of my processes to manipulate any of my
> > other processes' network connections (though I've not tested in detail to
> > see what's possible.)
>
> So you're saying that (a) a jailed process should not have access to
> the #-devices at all and (b) their equivalent /proc, /srv and /net
> ought to be configured as part of the jail and should not be
> modifiable.
Sounds about right. I'd say that they can be modifiable if new capabilities
are sendfd()'d into the namespace, but yes.
> Plan 9 source often short-circuits the possibility that #-something is
> not bound to the conventional place (#v comes to mind as a frequent
> culprit) but that is a form of laziness that could be corrected by a
> careful source audit. In which case it would be possible to treat #X
> as another of those security issues that needed special treatment for
> Factotum and have a kernel request that puts the #-space out of
> bounds.
Elsewhere in a different thread, eric grepped for explicit uses of #X paths
and found very few. See <3598a04c733942f7f010ad61d83a8bc2@quanstro.net>.
> Would that satisfy your requirements? Oh, sure, I haven't ever used
> #| directly and I'm a bit ignorant of consequences, but the rest seems
> feasible.
I suspect #| being an exception wouldn't hurt, though it might be viewed as
a historical wart, being the only one... could #| be made to operate more
like devdup and given a canonical mountpoint?
> Another aspect I noticed is that what you seem to need is a
> finer-grained construction of #p and #s, but being able to construct
> them one layer further down the hierarchy might suffice.
"one layer further down the hierarchy" ?
> Just an uneducated opinion, I've had little occasion to study those
> specific devices or the others in any detail. But I am curious of
> where this discussion could lead.
I too.
--nwf;
[-- Attachment #2: Type: application/pgp-signature, Size: 204 bytes --]
next prev parent reply other threads:[~2009-01-04 5:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 18:01 Nathaniel W Filardo
2008-12-23 22:52 ` Rodolfo kix Garcia
2008-12-23 23:53 ` Francisco J Ballesteros
2008-12-24 1:10 ` Nathaniel W Filardo
2008-12-24 1:39 ` erik quanstrom
2008-12-24 3:00 ` Nathaniel W Filardo
2008-12-24 4:14 ` erik quanstrom
2008-12-24 7:36 ` Nathaniel W Filardo
2008-12-24 13:36 ` erik quanstrom
2008-12-27 20:27 ` Roman Shaposhnik
2008-12-27 20:34 ` Eric Van Hensbergen
2008-12-27 20:21 ` Roman Shaposhnik
2008-12-30 8:22 ` Nathaniel W Filardo
2008-12-30 15:04 ` Eric Van Hensbergen
2008-12-30 15:31 ` erik quanstrom
2009-01-01 22:53 ` Roman V. Shaposhnik
2009-01-01 23:57 ` Nathaniel W Filardo
2009-01-03 21:23 ` Roman V. Shaposhnik
2009-01-03 21:41 ` erik quanstrom
2009-01-03 21:59 ` Roman V. Shaposhnik
2009-01-03 23:57 ` Nathaniel W Filardo
2009-01-04 5:19 ` lucio
2009-01-04 5:48 ` erik quanstrom
2009-01-04 6:10 ` Nathaniel W Filardo
2009-01-04 6:43 ` lucio
2009-01-05 1:12 ` Roman V. Shaposhnik
2009-01-05 1:32 ` erik quanstrom
2009-01-05 3:48 ` lucio
2009-01-04 17:32 ` erik quanstrom
2009-01-04 18:23 ` lucio
2009-01-05 1:24 ` Roman V. Shaposhnik
2009-01-04 5:58 ` Nathaniel W Filardo [this message]
2009-01-04 6:26 ` lucio
2009-01-04 15:46 ` erik quanstrom
2009-01-05 4:30 ` Roman V. Shaposhnik
2008-12-24 1:17 ` Nathaniel W Filardo
2008-12-27 17:06 ` Russ Cox
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=20090104055830.GI8355@masters10.cs.jhu.edu \
--to=nwf@cs.jhu.edu \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).