From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] allow
Date: Fri, 14 Jul 2000 20:25:46 -0400 [thread overview]
Message-ID: <20000714235707.287.qmail@nx.aichi-u.ac.jp> (raw)
In-Reply-To: <200007141418.KAA00244@cse.psu.edu>
Hello,
Rob Pike said:
>Better ideas (short of a superuser) are welcome.
and pip@stricca.org:
>Maybe the use of smart cards might be a solution.
I think it is an illusion that we can protect local file system
from someone who can touch keyboard of the machine.
Plan9 has a good solution for the terminals that are shared by
more than one person. That is, "it is best to purge local file
systems."
On the other hand, There are terminals that are used and managed
by a single person. We need not worry about malicious operations
by the owner. I believe kfs is intended for this case.
UNIX "root" is a formal administrative account. The account worked
well until machines were very expensive. But now every one can have
machines that run UNIX; and then, inconvenience and insecureness are
left for us.
Plan9 introduced "host owner" instead of "root". Both govern the
machine. Therefore they are superusers.
I think problem with kfs is in that it does not make distinguish
between "host owner" and others.
"host owner" is, in fact, a special user in terminals and/or
servers.
Therefore, I think some operations should be limited only to host
owner.
For example, "disk/kfscmd allow" should allow only to host owner to
ignore access permission.
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next prev parent reply other threads:[~2000-07-15 0:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 14:18 rob pike
2000-07-15 0:25 ` arisawa [this message]
2000-07-15 16:20 ` arisawa
2000-07-14 18:51 pip
2000-07-15 0:18 ` Randolph Fritz
2000-07-16 22:54 presotto
2000-07-17 15:11 ` Douglas A. Gwyn
2000-07-17 21:14 ` arisawa
2005-02-07 7:11 tapique
2005-02-07 7:31 ` Lucio De Re
2005-02-07 10:19 ` Heiko Dudzus
2005-02-07 10:57 ` Lucio De Re
2005-02-07 7:32 ` arisawa
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=20000714235707.287.qmail@nx.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).