From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] namespace construction
Date: Sat, 27 Nov 2004 20:59:52 +0900 [thread overview]
Message-ID: <D877FC06-406B-11D9-9E13-000393A941BC@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <200411262259.iAQMxj920959@zamenhof.cs.utwente.nl>
Hello,
I have two questions on namespace construction.
1st:
Let alice executes:
void
main(int argc, char *argv[])
{
rfork(RFCNAMEG);
bind("#c", "/dev", MAFTER);
execute("/boot/factotum", "factotum -n");
print_owner("/mnt/factotum/ctl")
}
where execute() is fork + exec + wait
and print_owner prints file owner.
then the program will print "alice"
however if bind is commented out, it print "none"
Is this a specification ?
2nd:
we will find the line:
ai = fauth_proxy(afd, rpc, amount_getkey, "proto=p9any
role=client");
in /sys/src/libauth/newns.c
note that user name is not specified here.
this can cause unexpected result.
for example, let factotum key for alice is:
key proto=p9sk1 dom=aichi-u.ac.jp user=alice !password?
key proto=p9sk1 dom=aichi-u.ac.jp user=bob !password?
then fauth_proxy will always get alice's key and constructs namespace
for alice even if alice want to be bob.
another example is:
if alice puts factotum keys into secstore
key proto=p9sk1 dom=aichi-u.ac.jp user=bob !password?
key proto=p9sk1 dom=aichi-u.ac.jp user=alice !password?
then alice will surprise to find that the namespace is not for alice.
why user is not specified in fauth_proxy ?
Kenji Arisawa
next prev parent reply other threads:[~2004-11-27 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 0:09 [9fans] sokoban YAMANASHI Takeshi
2004-09-07 0:13 ` andrey mirtchovski
2004-09-07 0:34 ` Russ Cox
2004-11-26 22:59 ` Axel Belinfante
2004-11-27 11:59 ` arisawa [this message]
2004-11-27 15:38 ` [9fans] namespace construction Heiko Dudzus
2004-11-27 17: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=D877FC06-406B-11D9-9E13-000393A941BC@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@cse.psu.edu \
/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).