mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Bodo Eggert <7eggert@gmx.de>
Cc: James Morris <jmorris@namei.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: TOMOYO in linux-next
Date: Sun, 29 Mar 2009 13:58:30 +0200	[thread overview]
Message-ID: <20090329115830.GA15492@elf.ucw.cz> (raw)
In-Reply-To: <alpine.LSU.0.999.0903271354290.5610@be1.lrz>

On Fri 2009-03-27 14:04:32, Bodo Eggert wrote:
> On Fri, 27 Mar 2009, Pavel Machek wrote:
> > On Fri 2009-03-27 10:28:07, Bodo Eggert wrote:
> > > Pavel Machek <pavel@ucw.cz> wrote:
> 
> > > > I don't think merging that is good idea. Security should be doable
> > > > without making shell-like glob matching...
> > > 
> > > How do you suppose a security system should handle mozilla modifying
> > > ~/.bashrc differently from downloading something to ~/pr0n.jpg?
> > 
> > How does shell-like glob matching help there? You'd need to parse
> > /etc/passwd to find all ~ directories...
> 
> That is, if you'd use HOME=`dd if=/dev/urandom ...`.
> 
> If you have your users in /home/user, you can tell /home/*/.*
> is bad, /home/*/[^.]* is OK.

On the common systems I know of, homes are spread over different
volumes and different directories. TOMOYO's wildcards do _not_ solve
this particular problems.

> How would you exclude mozilla from writing to .* then? ".a" is bad,
> ".b" is bad ...? or "A" is OK, "a" is OK, "zzzzzzzzzzzzz" is OK"?
> Either way, you'd need several universes to store the security profile.

What is magic about .* files? I want mozilla to store the pictures as
.naughty.picture.jpg -- I don't see anything wrong with that.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-03-29 11:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ck5CF-5mU-11@gated-at.bofh.it>
2009-03-27  9:28 ` Bodo Eggert
2009-03-27 11:42   ` Pavel Machek
2009-03-27 13:04     ` Bodo Eggert
2009-03-29 11:58       ` Pavel Machek [this message]
2009-03-29 14:25         ` Bodo Eggert
2009-03-29 21:39           ` Pavel Machek
2009-03-30 11:22             ` Bodo Eggert
2009-03-26 21:50 Pavel Machek
2009-03-27  0:15 ` James Morris
2009-03-27  0:30   ` Pavel Machek
2009-03-27  0:51     ` James Morris
2009-03-27 11:36       ` Pavel Machek
2009-03-27  0:36   ` Pavel Machek
2009-03-27  0:46     ` James Morris
2009-03-27 11:35       ` Pavel Machek
2009-03-27  4:12   ` Tetsuo Handa
2009-03-27  8:04     ` James Morris
2009-03-27 11:40     ` Pavel Machek
2009-04-06 11:49     ` Tetsuo Handa
2009-04-06 12:01       ` Pavel Machek
2009-04-06 22:21       ` James Morris

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=20090329115830.GA15492@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=7eggert@gmx.de \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®