From: Frank v Waveren <fvw@var.cx>
To: Werner Almesberger <wa@almesberger.net>
Cc: Robert Love <rml@tech9.net>, Julien Oster <frodo@dereference.de>,
linux-kernel@vger.kernel.org
Subject: Re: kernel ring buffer accessible by users
Date: Wed, 23 Apr 2003 18:59:31 +0200 [thread overview]
Message-ID: <1051117076FZS.fvw@jareth.var.cx> (raw)
In-Reply-To: <20030423134530.C3557@almesberger.net>
On Wed, Apr 23, 2003 at 01:45:30PM -0300, Werner Almesberger wrote:
> Yes, but you'll get quite a few objections to adding yet another
> suid root program :-)
Why not make it mode 440, and have a mount option for the proc
filesystem that gives which gid certain sensitive files should have.
The openwall security patch does this (with a few further restrictions
to the permissions of certain /proc files) and I like it a lot.
--
Frank v Waveren Fingerprint: 21A7 C7F3
fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100 1FF3 47FF 545C CB53
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx 7BD9 09C0 3AC1 6DF2
next prev parent reply other threads:[~2003-04-23 16:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 16:21 kernel ring buffer accessible by users Julien Oster
2003-04-22 16:44 ` Michael Buesch
2003-04-22 16:52 ` Grzegorz Jaskiewicz
2003-04-22 16:54 ` Jörn Engel
2003-04-22 16:54 ` Julien Oster
2003-04-22 17:54 ` Richard B. Johnson
2003-04-22 17:17 ` Robert Love
2003-04-23 15:56 ` Werner Almesberger
2003-04-23 15:59 ` Robert Love
2003-04-23 16:23 ` Werner Almesberger
2003-04-24 0:30 ` David Wagner
2003-04-24 14:02 ` Grzegorz Jaskiewicz
2003-04-23 16:05 ` Julien Oster
2003-04-23 16:45 ` Werner Almesberger
2003-04-23 16:59 ` Frank v Waveren [this message]
2003-04-24 0:31 ` David Wagner
2003-04-24 13:10 ` Stephan von Krawczynski
2003-04-22 19:53 ` Jason Cook
2003-04-23 9:33 ` Olaf Hering
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=1051117076FZS.fvw@jareth.var.cx \
--to=fvw@var.cx \
--cc=frodo@dereference.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=wa@almesberger.net \
/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