From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Restrict procfs permissions
Date: Sat, 29 Jan 2005 04:41:09 +0000 [thread overview]
Message-ID: <20050129044109.GR8859@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050129024542.GB12270@lsrfire.ath.cx>
On Sat, Jan 29, 2005 at 03:45:42AM +0100, Rene Scharfe wrote:
> The patch is inspired by the /proc restriction parts of the GrSecurity
> patch. The main difference is the ability to configure the restrictions
> dynamically. You can change the umask setting by running
>
> # mount -o remount,umask=007 /proc
>
> Testing has been *very* light so far -- it compiles and boots. Patch is
> against 2.6.11-rc2-bk6.
>
> Comments are very welcome.
It leaves already existing inodes with whatever mode they used to have.
_IF_ you want to do that sort of things, do it right - add ->permission()
that would apply that umask before checks and if you want it to be seen
in results of stat(2) - add ->gettattr() and do the same there.
next prev parent reply other threads:[~2005-01-29 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 2:45 Rene Scharfe
2005-01-29 4:41 ` Al Viro [this message]
2005-01-29 19:18 ` Rene Scharfe
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=20050129044109.GR8859@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.scharfe@lsrfire.ath.cx \
/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
Powered by JetHome