From: Miles Lane <miles@megapathdsl.net>
To: David Lang <dlang@diginsite.com>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: bug database braindump from the kernel summit
Date: Sun, 01 Apr 2001 18:57:25 -0700 [thread overview]
Message-ID: <3AC7DC85.CED53440@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0104011415320.25794-100000@dlang.diginsite.com>
David Lang wrote:
>
> On Sun, 1 Apr 2001, Larry McVoy wrote:
>
> when generating the auto bug reports make sure that the system tells the
> user exactly what data is being sent.
>
> sending a large chunk of unknown data off the machine is a big concern to
> many people.
Yeah. This is a good point, although I can't think of info
about a system's hardware and software configuration that would
be particularly sensitive, other than files that contain network
topology or encrypted passwords. I'm sure others can come up
with such a list. One candidate might be the smbfs configuration
file, since network passwords can live there, right? tcpdump output
might also be sensitive, but that type of info would need to get
requested by network driver developers after the initial bug report
anyhow.
Miles
next prev parent reply other threads:[~2001-04-02 2:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 17:54 bug database braindump from the kernel summit Larry McVoy
2001-04-01 19:43 ` Albert D. Cahalan
2001-04-01 20:21 ` Gregory Maxwell
2001-04-01 20:38 ` Albert D. Cahalan
2001-04-01 21:16 ` David Lang
2001-04-01 21:18 ` David Lang
2001-04-02 1:57 ` Miles Lane [this message]
2001-04-02 5:07 ` David Lang
2001-04-01 23:14 ` Jeff Garzik
2001-04-02 13:31 ` Rogier Wolff
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 19:32 Manfred Spraul
2001-04-01 20:17 ` Albert D. Cahalan
2001-04-01 21:07 ` Jeff Garzik
2001-04-01 21:48 ` Manfred Spraul
2001-04-01 22:48 ` Jeff Garzik
2001-04-01 23:01 ` David Lang
2001-04-01 23:21 ` Jeff Garzik
2001-04-01 23:25 ` David Lang
2001-04-01 23:34 ` Jeff Garzik
2001-04-01 23:32 ` David Lang
2001-04-01 23:44 ` Jeff Garzik
2001-04-01 23:43 ` David Lang
2001-04-02 0:26 ` Ben Ford
2001-04-02 18:57 ` Kai Henningsen
2001-04-05 12:55 ` Petr Baudis
2001-04-02 5:26 ` Richard Russon
2001-04-02 21:35 ` Steven Walter
2001-04-02 19:39 ` Oliver Xymoron
2001-04-02 21:40 ` J . A . Magallon
2001-04-02 22:09 ` Jeff Garzik
2001-04-02 22:24 ` David Lang
2001-04-02 22:38 ` J . A . Magallon
2001-04-02 23:04 ` Tom Leete
2001-04-02 23:12 ` Oliver Xymoron
2001-04-02 23:24 ` Jeff Garzik
2001-04-02 23:31 ` Oliver Xymoron
2001-04-03 16:05 ` Miles Lane
2001-04-02 1:49 ` Miles Lane
2001-04-01 20:59 ` Jeff Garzik
2001-04-01 22:34 Stephen Satchell
2001-04-02 8:00 ` Olaf Titz
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=3AC7DC85.CED53440@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=dlang@diginsite.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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.