public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Al Viro <viro@ftp.linux.org.uk>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	torvalds@osdl.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, akpm@osdl.org, paul.moore@hp.com
Subject: Re: [PATCH] Version 4 (2.6.23-rc8-mm2) Smack: Simplified Mandatory Access Control Kernel
Date: Wed, 3 Oct 2007 13:21:32 -0700 (PDT)	[thread overview]
Message-ID: <342112.80881.qm@web36601.mail.mud.yahoo.com> (raw)
In-Reply-To: <20071003191735.4d92c593@the-village.bc.nu>


--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > Absolute paths in that kind of thing are _wrong_.  You know where the
> things
> > are on your fs.  You don't know if anything else will be visible, let alone
> > whether it will be at the same place in all chroots or namespaces.  And no,
> > you _can't_ make sure that fs is visible only in one place.  No fs can or
> > has any business even trying.
> 
> What I don't understand here is why we need the hacks when we already
> support sufficient mount magic to give each login session its own
> private /tmp ?

An embedded system that does not have user logins but that does
have applications that require separation, perhaps a moble communication
device with application download capability, is just one example
where the smack symlink implementation provides the required
function without requiring application support.
 

Casey Schaufler
casey@schaufler-ca.com

  parent reply	other threads:[~2007-10-03 20:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03  4:45 [PATCH] Version 4 (2.6.23-rc8-mm2) Smack: Simplified Mandatory Access Control Kernel Casey Schaufler
2007-10-03  5:12 ` Al Viro
2007-10-03 17:21   ` Casey Schaufler
2007-10-03 17:52     ` Al Viro
2007-10-03 18:17       ` Alan Cox
2007-10-03 18:17         ` Al Viro
2007-10-03 20:21         ` Casey Schaufler [this message]
2007-10-03 20:40           ` Alan Cox
2007-10-03 21:06             ` Casey Schaufler
2007-10-03 19:51       ` Casey Schaufler
2007-10-03 20:57         ` Al Viro
2007-10-03 22:23           ` Casey Schaufler
2007-10-03 22:50             ` Al Viro
2007-10-04  0:42               ` Casey Schaufler
2007-10-03 12:19 ` Paul Moore

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=342112.80881.qm@web36601.mail.mud.yahoo.com \
    --to=casey@schaufler-ca.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul.moore@hp.com \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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