From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] sendfd() on native Plan 9?
Date: Tue, 23 Dec 2008 20:39:27 -0500 [thread overview]
Message-ID: <458d6ee210e735a9603280e2af71077e@quanstro.net> (raw)
In-Reply-To: <20081224011053.GP9593@masters10.cs.jhu.edu>
> /srv is not an ideal answer, though it is the one I feared would be given.
> /srv allows any process running as a given user to access the posted fd, and
> does not respect namespace or process group boundaries. I want a mechanism
> to pass a file descriptor to one target process so that I can pass an fd
> across namespaces without giving _all_ namespaces access to said fd.
>
> A /srv that 1) was not enumerable, 2) allowed only single opens, and 3) used
> secure identifiers (capabilities, similar to devcap) would suffice, as
> processes could post an fd to recieve an identifier, pass the identifiers to
> another process, and then turn the identifier into an fd.
on unix, which is not a distributed system, passing fds around makes
a certain amount of sense. in plan 9, i would think that the ideal
answer would need to allow for the unrelated processes running
on seperate machine. i would also think that it would allow the
standard authentication mechanisms to work. fds really don't fit
either one of those criteria. but we're talking generalities. what's the
specific application?
- erik
next prev parent reply other threads:[~2008-12-24 1:39 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 [this message]
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
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=458d6ee210e735a9603280e2af71077e@quanstro.net \
--to=quanstro@quanstro.net \
--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).