From: Pavel Machek <pavel@ucw.cz>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, takedakn@nttdata.co.jp,
hch@infradead.org
Subject: Re: [TOMOYO 5/9] Memory and pathname management functions.
Date: Thu, 21 Jun 2007 20:22:05 +0200 [thread overview]
Message-ID: <20070621182205.GB18990@elf.ucw.cz> (raw)
In-Reply-To: <787b0d920706160208u62f8a2c5q5f94f5986d755d24@mail.gmail.com>
Hi!
> >> It's really not worth getting bothered by. Truth is, big
> >> giant
> >> pathnames break lots of stuff already, both kernel and
> >> userspace.
> >
> >> Just look in /proc for some nice juicy kernel breakage:
> >> cwd, exe, fd/*, maps, mounts, mountstats, root, smaps
> >
> >Well, but we should be fixing that, not adding more. And /proc is
> >info-only, while this is security related code.
>
> Security tools read from /proc, so /proc is security-related.
If some tool relies on pathnames in /proc, that tool is broken... as
is /proc. We should be fixing that.
> The limit imposed by TOMOYO (or AppArmor) is fine,
> despite being security-related. It just needs to fail in
It is not "fine", but maybe it will not get us a bugtraq posting.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-06-21 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 7:16 Albert Cahalan
2007-06-15 13:00 ` Pavel Machek
2007-06-16 9:08 ` Albert Cahalan
2007-06-21 18:22 ` Pavel Machek [this message]
2007-06-22 14:45 ` Albert Cahalan
-- strict thread matches above, loose matches on Subject: below --
2007-06-14 7:30 [TOMOYO 0/9] TOMOYO Linux security module Kentaro Takeda
2007-06-14 7:36 ` [TOMOYO 5/9] Memory and pathname management functions Kentaro Takeda
2007-06-14 17:34 ` Christoph Hellwig
2007-06-15 1:19 ` Toshiharu Harada
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=20070621182205.GB18990@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=acahalan@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=takedakn@nttdata.co.jp \
/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®