From: Jason Cook <jasonc@reinit.org>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel ring buffer accessible by users
Date: Tue, 22 Apr 2003 15:53:04 -0400 [thread overview]
Message-ID: <20030422195304.GQ11056@panacea.canonical.org> (raw)
In-Reply-To: <frodoid.frodo.87wuhmh5ab.fsf@usenet.frodoid.org>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
* Julien Oster (frodo@dereference.de) wrote:
>
> Hello,
>
> it's been quite a while that I noticed that any ordinary user, not
> just root, can type "dmesg" to see the kernel ring buffer.
>
> My question now is: Why? I often saw things in the kernel ring buffer
> which I don't want every user to know (e.g. some telephone numbers with
> ISDN).
>
> Are there any problems in just letting root get the contents of the
> kernel ring buffer?
>
> Julien
> -
grsec has an option to do this:
http://www.grsecurity.net/
--
Jason Cook | GnuPG Fingerprint: D531 F4F4 BDBF 41D1 514D
GNU/Linux Engineering Lead | F930 FD03 262E 5120 BEDD
evolServ Technology | Home page: http://reinit.org
cthread. cthread_fork(). Fork, thread, fork!
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-04-22 19:43 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
2003-04-24 0:31 ` David Wagner
2003-04-24 13:10 ` Stephan von Krawczynski
2003-04-22 19:53 ` Jason Cook [this message]
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=20030422195304.GQ11056@panacea.canonical.org \
--to=jasonc@reinit.org \
--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;
as well as URLs for NNTP newsgroup(s).