From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: "\"\\\"Serge E. Hallyn\\\"\"" <serue@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux Containers <containers@lists.osdl.org>
Subject: Re: [patch 1/2] [RFC] Simple tamper-proof device filesystem.
Date: Tue, 18 Dec 2007 11:26:21 +0900 [thread overview]
Message-ID: <200712180226.lBI2QL1d020811@www262.sakura.ne.jp> (raw)
In-Reply-To: <20071218015557.GA28652@sergelap.austin.ibm.com>
Hello.
Serge E. Hallyn wrote:
> But your requirements are to ensure that an application accessing a
> device at a well-known location get what it expect.
Yes. That's the purpose of this filesystem.
> So then the main quesiton is still the one I think Al had asked - what
> keeps a rogue CAP_SYS_MOUNT process from doing
> mount --bind /dev/hda1 /dev/null ?
Excuse me, but I guess you meant "mount --bind /dev/ /root/" or something
because mount operation requires directories.
MAC can prevent a rogue CAP_SYS_MOUNT process from doing
"mount --bind /dev/ /root/".
For example, regarding TOMOYO Linux, you need to give
"allow_mount /dev/ /root/ --bind 0" permission
to permit "mount --bind /dev/ /root/" request.
Did you mean "ln -s /dev/hda1 /dev/null" or "ln /dev/hda1 /dev/null"?
No problem. MAC can prevent such requests too.
Regards.
next prev parent reply other threads:[~2007-12-18 2:26 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071216080441.435456586@I-love.SAKURA.ne.jp>
[not found] ` <20071216080628.061470932@I-love.SAKURA.ne.jp>
2007-12-16 10:44 ` [patch 0/2] [RFC] Simple tamper-proof device filesystem Tetsuo Handa
2007-12-16 10:56 ` [patch 1/2] " Tetsuo Handa
2007-12-06 15:29 ` Pavel Machek
2007-12-18 15:55 ` Valdis.Kletnieks
2007-12-18 16:43 ` Casey Schaufler
2007-12-16 11:21 ` David Newall
2007-12-16 11:26 ` Tetsuo Handa
2007-12-16 11:31 ` David Newall
2007-12-16 11:36 ` Tetsuo Handa
2007-12-16 11:58 ` David Newall
2007-12-16 12:03 ` Tetsuo Handa
2007-12-16 12:14 ` Tetsuo Handa
2007-12-17 6:00 ` David Newall
2007-12-18 15:33 ` Radoslaw Szkodzinski
2007-12-16 16:52 ` Indan Zupancic
2007-12-16 19:48 ` Al Viro
2007-12-17 0:40 ` Tetsuo Handa
2007-12-17 11:44 ` Indan Zupancic
2007-12-17 12:59 ` Tetsuo Handa
2007-12-17 13:05 ` Al Boldi
2007-12-17 13:16 ` Tetsuo Handa
2007-12-18 15:22 ` Radoslaw Szkodzinski
2007-12-19 12:11 ` Tetsuo Handa
2007-12-19 19:14 ` Radoslaw Szkodzinski
2007-12-17 13:32 ` Tetsuo Handa
2007-12-17 6:42 ` penguin-kernel
2007-12-17 19:48 ` Serge E. Hallyn
[not found] ` <20071217194802.GA14156-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-12-18 0:03 ` Tetsuo Handa
2007-12-18 0:39 ` Serge E. Hallyn
2007-12-18 1:39 ` Oren Laadan
2007-12-18 2:09 ` Serge E. Hallyn
2007-12-18 3:04 ` Oren Laadan
2007-12-19 9:43 ` Pavel Emelyanov
2007-12-19 14:10 ` Serge E. Hallyn
2007-12-20 0:07 ` Oren Laadan
2007-12-20 7:42 ` Pavel Emelyanov
2007-12-20 14:09 ` Serge E. Hallyn
[not found] ` <476A1CE0.30505-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-12-21 1:47 ` Oren Laadan
2007-12-19 14:13 ` Serge E. Hallyn
2007-12-18 1:55 ` Serge E. Hallyn
2007-12-18 2:26 ` Tetsuo Handa [this message]
2007-12-18 2:53 ` serge
2007-12-18 3:40 ` Tetsuo Handa
2007-12-19 23:43 ` Serge E. Hallyn
2007-12-24 13:09 ` Tetsuo Handa
2007-12-16 11:03 ` [patch 2/2] " Tetsuo Handa
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=200712180226.lBI2QL1d020811@www262.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=containers@lists.osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.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;
as well as URLs for NNTP newsgroup(s).