From: Werner Almesberger <wa@almesberger.net>
To: Robert Love <rml@tech9.net>
Cc: Julien Oster <frodo@dereference.de>, linux-kernel@vger.kernel.org
Subject: Re: kernel ring buffer accessible by users
Date: Wed, 23 Apr 2003 12:56:03 -0300 [thread overview]
Message-ID: <20030423125602.B1425@almesberger.net> (raw)
In-Reply-To: <1051031876.707.804.camel@localhost>; from rml@tech9.net on Tue, Apr 22, 2003 at 01:17:57PM -0400
Robert Love wrote:
> I think the problem is that kernel messages should not contain private
> information, like ISDN phone numbers. Why is that even in the kernel?
How do you know what is sensitive information ? A kernel debug
message may just say something like "bad message 47 65 68 65 69 6d",
and the kernel has no idea that this is actually a password
("Geheim").
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2003-04-23 15:44 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 [this message]
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
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=20030423125602.B1425@almesberger.net \
--to=wa@almesberger.net \
--cc=frodo@dereference.de \
--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 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).