From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: David Howells <dhowells@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, openafs-devel@openafs.org
Subject: Re: [PATCH] in-core AFS multiplexor and PAG support
Date: 13 May 2003 17:39:15 +0100 [thread overview]
Message-ID: <1052843954.431.84.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0305130950030.1678-100000@home.transmeta.com>
On Maw, 2003-05-13 at 17:57, Linus Torvalds wrote:
> A "user" is by definition what the unix filesystem considers to be the
> "atom of security". In fact, a "user" has no other meaning - except for
> the notion of "root", which is obviously special and has meaning outside
> of the scope of filesystems (and even here capabilities have tried to
> separate out that meaning from the "user" definition).
This has been untrue since the security hooks went in, and in some
senses before that (capabilities mean multiple "root"'s)
> "role" that is shared across processes. But I think that for _usability_
> we really want that to be _shared_ by default, and anybody who wants to
> split it should have to work at it. Exactly so that when you log in, and
> use your private key to mount some encrypted volume, _all_ your processes
> should by default get access to it. Even if the other ones were
> independent logins (another window with another ssh session to that
> machine).
>
> In other words: I really think usability should count very high on the
> list of requirements. Much higher than SELinux.
Sounds right. PAM can certainly do the splitting providing the functionality
is there to do it
next prev parent reply other threads:[~2003-05-13 17:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 15:39 David Howells
2003-05-13 15:52 ` Linus Torvalds
2003-05-13 15:44 ` Alan Cox
2003-05-13 16:52 ` Jan Harkes
2003-05-13 16:57 ` Linus Torvalds
2003-05-13 16:39 ` Alan Cox [this message]
2003-05-13 21:46 ` [OpenAFS-devel] " Russ Allbery
2003-05-16 15:38 ` Derek Atkins
2003-05-13 16:05 ` David Howells
2003-05-13 16:24 ` [OpenAFS-devel] " Douglas E. Engert
2003-05-13 16:47 ` Linus Torvalds
2003-05-13 17:20 ` Jan Harkes
2003-05-13 18:21 ` David Howells
2003-05-13 18:51 ` [OpenAFS-devel] " Douglas E. Engert
2003-05-13 20:33 ` Jan Harkes
2003-05-13 21:26 ` Douglas E. Engert
2003-05-13 21:40 ` Jan Harkes
2003-05-13 22:14 ` Douglas E. Engert
2003-05-14 2:02 ` Jan Harkes
2003-05-17 12:30 ` Pavel Machek
2003-05-18 14:22 ` [OpenAFS-devel] " Nathan Neulinger
2003-05-18 18:06 ` Pavel Machek
2003-05-13 17:23 ` Trond Myklebust
2003-05-15 11:41 ` Ingo Oeser
2003-05-13 17:42 ` David Howells
2003-05-13 16:03 ` Christoph Hellwig
2003-05-13 16:12 ` David Howells
2003-05-13 20:23 ` Christoph Hellwig
2003-05-13 16:39 ` Jeff Garzik
2003-05-13 16:57 ` David Howells
[not found] <20030513182950.GB30766@delft.aura.cs.cmu.edu>
2003-05-13 18:53 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 15:34 David Howells
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=1052843954.431.84.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openafs-devel@openafs.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®