From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Sun, 14 Nov 2010 17:49:25 -0500 [thread overview]
Message-ID: <20101114224925.GB21298@gradx.cs.jhu.edu> (raw)
In-Reply-To: <AANLkTi=fTWYdgCo3HTWAjkz=weWL7Y_Q=LTQVuXOZBaj@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Fri, Nov 12, 2010 at 02:20:35PM -0800, ron minnich wrote:
> On Fri, Nov 12, 2010 at 2:15 PM, Eric Van Hensbergen <ericvh@gmail.com> wrote:
>
> > No, that's true. I think this is actually a huge open issue for
> > existing distributed file systems in general and I'm not sure of a
> > good way around.
>
> yeah, we had lots of discussion of this about 8 years ago with 9grid
> and never worked it out.
One proposal would be...
> What's your global identify?
A public (SPKI) key or, more robustly, a halo of subkeys.
> How do you name it?
By the shortest path from the key currently used as root, which probably is
the same as your public identity, so it gets stringified as "" or "." or
"self" or somesuch.
> How do you map it to a local identity?
There's less need to, since most rights checks would be done using the key
directly, but eve's factotum also probably has a SPKI key, and your identity
can be stringified into a path of names if necessary.
--nwf;
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2010-11-14 22:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:13 erik quanstrom
2010-11-09 3:37 ` erik quanstrom
2010-11-09 17:41 ` David Leimbach
2010-11-09 17:51 ` erik quanstrom
2010-11-10 0:37 ` erik quanstrom
2010-11-10 1:49 ` Russ Cox
2010-11-10 6:46 ` erik quanstrom
2010-11-10 14:31 ` Russ Cox
2010-11-12 3:35 ` Noah Evans
2010-11-12 5:34 ` erik quanstrom
2010-11-12 5:46 ` Noah Evans
2010-11-12 6:03 ` Noah Evans
2010-11-12 6:19 ` Russ Cox
2010-11-12 6:25 ` Noah Evans
2010-11-12 9:07 ` EBo
2010-11-12 15:12 ` David Leimbach
2010-11-12 15:19 ` Eric Van Hensbergen
2010-11-12 15:35 ` erik quanstrom
2010-11-12 15:55 ` Russ Cox
2010-11-12 16:22 ` Eric Van Hensbergen
2010-11-12 19:55 ` ron minnich
2010-11-12 20:23 ` erik quanstrom
2010-11-12 20:31 ` Eric Van Hensbergen
2010-11-12 20:37 ` ron minnich
2010-11-12 20:30 ` Eric Van Hensbergen
2010-11-12 20:41 ` ron minnich
2010-11-12 22:15 ` Eric Van Hensbergen
2010-11-12 22:20 ` ron minnich
2010-11-12 22:36 ` Russ Cox
2010-11-13 8:31 ` tlaronde
2010-11-13 23:42 ` Dave Eckhardt
2010-11-14 22:49 ` Nathaniel W Filardo [this message]
2010-11-15 16:22 ` erik quanstrom
2010-11-15 17:40 ` Nathaniel W Filardo
2010-11-15 17:50 ` John Floren
2010-11-12 21:12 ` Russ Cox
2010-11-09 18:08 ` yy
2010-11-09 19:17 ` Bakul Shah
2010-11-09 19:27 ` 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=20101114224925.GB21298@gradx.cs.jhu.edu \
--to=nwf@cs.jhu.edu \
--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).