From: Stephan von Krawczynski <skraw@ithnet.com>
To: daw@mozart.cs.berkeley.edu (David Wagner)
Cc: frodoid@frodoid.org, rml@tech9.net, frodo@dereference.de,
linux-kernel@vger.kernel.org, wa@almesberger.net
Subject: Re: kernel ring buffer accessible by users
Date: Thu, 24 Apr 2003 15:10:21 +0200 [thread overview]
Message-ID: <20030424151021.69b34400.skraw@ithnet.com> (raw)
In-Reply-To: <b87b8q$sks$3@abraham.cs.berkeley.edu>
On 24 Apr 2003 00:31:22 GMT
daw@mozart.cs.berkeley.edu (David Wagner) wrote:
> 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.
>
> Would it? I can't think of anything that currently should be printed
> to the ring buffer and is known to be secret.
The simple truth is: you cannot really qualify what a "secret" is or is not. It
depends on the _reader_(s' interest), not the _writer_ (s' intention).
Regards,
Stephan
next prev parent reply other threads:[~2003-04-24 12:58 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 [this message]
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=20030424151021.69b34400.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=daw@mozart.cs.berkeley.edu \
--cc=frodo@dereference.de \
--cc=frodoid@frodoid.org \
--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;
as well as URLs for NNTP newsgroup(s).