From: "Kristian Sørensen" <ks@cs.aau.dk>
To: Tetsuo Handa <from-linux-kernel@i-love.sakura.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][2.4 PATCH] A restricted /dev filesystem.
Date: Mon, 1 Nov 2004 13:43:00 +0100 [thread overview]
Message-ID: <200411011343.00513.ks@cs.aau.dk> (raw)
In-Reply-To: <200411012114.IIG42981.tSSMNOFVtPMYFGLOJ@i-love.sakura.ne.jp>
Hi!
I see your point to some degree...
On Monday 01 November 2004 13:15, Tetsuo Handa wrote:
> Specifications:
>
> No regular files allowed. (since I think /dev needn't to keep regular
> files.) No hardlinks allowed. (since I think hardlinks are unused for /dev
> .)
Unless your work will be accepted in the vanilla kernel, you will might
consider making your code a bit more generic.
E.g. these two statements of disallowing creation of hardlinks and regular
files in /dev can easily be implemented as a LSM module (see
include/linux/security.h). (I think) You will need to consider the hooks
inode_create and inode_link only.
Cheers, KS.
--
Kristian Sørensen
- The Umbrella Project
http://umbrella.sourceforge.net
E-mail: ipqw@users.sf.net, Phone: +45 29723816
next prev parent reply other threads:[~2004-11-01 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 12:15 Tetsuo Handa
2004-11-01 12:43 ` Kristian Sørensen [this message]
2004-11-01 13:16 ` 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=200411011343.00513.ks@cs.aau.dk \
--to=ks@cs.aau.dk \
--cc=from-linux-kernel@i-love.sakura.ne.jp \
--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®