mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Wilkerson, Bryan P" <Bryan.P.Wilkerson@intel.com>
To: "Andrea Arcangeli" <andrea@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: KLive: Linux Kernel Live Usage Monitor
Date: Tue, 30 Aug 2005 10:08:38 -0700	[thread overview]
Message-ID: <194B303F2F7B534594F2AB2D87269D9F06EFAE48@orsmsx408> (raw)



On Tue, Aug 30, 2005 at 10:01:21AM +0200, Sven Ladegast wrote:
> The idea isn't bad but lots of people could think that this is some
kind 
> of home-phoning or spy software. I guess lots of people would turn
this 
> feature off...and of course you can't enable it by default. But
combined 
> with an automatic oops/panic/bug-report this would be _very_ useful I 
> think.

I think this is useful and would personally participate if it were a
config tweak.  There are a couple of issues that come to mind.  

1. Possibly paranoia, but given the apparent numbers of people with
malicious intent on the Internet and knowing that there are some
financially motivated to make Linux kernel developers over confident in
they're work, I'm not sure I'd trust or use the data unless it was
somehow authenticated.  

2. Some of us sit behind corporate firewalls and proxies that have
oppressive rules that would have made Stalin proud.  The solution must
be proxy aware and if it used HTTP, even better because it's more likely
to work anywhere.  The proxy settings could also be a .config thing.  

3. Again security; I haven't cleared this with my corporate superiors
but I'm not sure they'll like the fact that anyone could intercept the
data and compute how many people in the company are running Linux test
kernels.  I know this almost sounds anti-open but we're breaking them in
slowly to the model and I don't think they are ready for this one just
yet. :)

-bryan

             reply	other threads:[~2005-08-30 17:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 17:08 Wilkerson, Bryan P [this message]
2005-08-30 17:44 ` linux-os (Dick Johnson)
2005-08-30 20:31 ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2005-08-30  3:09 Andrea Arcangeli
2005-08-30  8:01 ` Sven Ladegast
2005-08-30  8:29   ` Rogier Wolff
2005-08-30  8:53     ` Sven Ladegast
2005-08-30  9:40       ` Rogier Wolff
2005-08-30  9:54         ` Bernd Petrovitsch
2005-08-30 15:10         ` Andrea Arcangeli
2005-08-30 16:33           ` Alan Cox
2005-08-30 16:16             ` Andrea Arcangeli
2005-08-30 16:56               ` Alan Cox
2005-08-30 16:40                 ` Andrea Arcangeli
2005-08-31 18:32               ` Pavel Machek
2005-09-01 15:19                 ` Andrea Arcangeli
2005-08-30 16:36             ` Jesper Juhl
2005-08-30 22:11         ` Bill Davidsen
2005-08-31  1:49           ` Andrea Arcangeli
2005-08-31 19:14             ` tony.luck
2005-08-31 19:47               ` Andrea Arcangeli
2005-09-05 18:26                 ` Andrea Arcangeli
2005-08-30 14:45     ` Andrea Arcangeli
2005-08-30 14:36   ` Alan Cox
2005-08-30 22:43     ` Sven Ladegast
2005-08-30 23:25       ` Alan Cox
2005-08-30 23:19         ` Sven Ladegast
2005-08-31 13:34           ` Alan Cox
2005-08-31 14:28             ` Sven Ladegast
2005-08-31 21:23               ` Andrea Arcangeli
2005-08-30 14:56   ` Andrea Arcangeli
2005-08-31 18:20     ` Pavel Machek
2005-09-01 15:23       ` Andrea Arcangeli
2005-09-01 12:26     ` Sven Ladegast
2005-09-05 22:05 ` Marc Giger
2005-09-05 23:13   ` Andrea Arcangeli

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=194B303F2F7B534594F2AB2D87269D9F06EFAE48@orsmsx408 \
    --to=bryan.p.wilkerson@intel.com \
    --cc=andrea@suse.de \
    --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

all inboxes | Powered by JetHome®