From: Werner Almesberger <wa@almesberger.net>
To: Julien Oster <frodoid@frodoid.org>
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 13:45:30 -0300 [thread overview]
Message-ID: <20030423134530.C3557@almesberger.net> (raw)
In-Reply-To: <20030423160556.GA30306@frodo.midearth.frodoid.org>; from frodoid@frodoid.org on Wed, Apr 23, 2003 at 06:05:56PM +0200
Julien Oster wrote:
> Of course one could say "then let's just stop writing out anything in
> the kernel buffer that COULD be sensitive", but I think this would
> actually castrate the meaning of such a buffer.
It's also bad security design to try to plug hundreds of potential
leaks, instead of the one common channel they share.
> And there's stillt he possibility to tweak the permissions for
> dmesg so that only a certain group (staff, operator, adm...) can execute
> it, but then setuid root.
Yes, but you'll get quite a few objections to adding yet another
suid root program :-)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2003-04-23 16:33 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 [this message]
2003-04-23 16:59 ` Frank v Waveren
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=20030423134530.C3557@almesberger.net \
--to=wa@almesberger.net \
--cc=frodo@dereference.de \
--cc=frodoid@frodoid.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.