All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Perkel <marc@perkel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Wiretapping Linux?
Date: Tue, 16 May 2006 06:56:05 -0700	[thread overview]
Message-ID: <4469D9F5.9030702@perkel.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0605160939290.10890@gandalf.stny.rr.com>



Steven Rostedt wrote:
> On Tue, 16 May 2006, Marc Perkel wrote:
>
>   
>> As most of you know the United States is tapping you telephone calls and
>> tracking every call you make. The next logical step is to start tapping
>> your computer implanting spyware into operating systems. Since Windows
>> and OS-X are proprietary this can be done more easilly with the
>> cooperation of Microsoft and Apple.
>>
>> So what about Linux? With thousands of people working on the Kernel if
>> someone from the NSA wanted to slip a back door into the Kernel, could
>> the do that?
>>     
>
> Well, yes and no.
>
> It's highly unlikely that it would get into the kernel. Definitely not
> kernel.org, since all patches are public.
>
> But it's not the kernel that you have to always worry about.  But it's
> what you install.  Especially as root.
>
> There's so much free stuff out there, that people download and install
> blindly, that I'm sure if someone wanted to really badly, they could get
> it on some boxes.  If they were slime and added something to a binary,
> and supplied the source without the backdoor, that might last a while.
> Unless you compile everything yourself, it's not easy to make sure that
> all binaries came from the source you have.
>
> But there are a lot of hackers out there (the good kind, not the crackers
> that the press call "hackers").  And they are aways looking at things
> and breaking them to see how they work.
>
> So, really, I doubt anyone could really get a lot on lots of people's
> Linux boxes.  But, if we ever had an evil Debian maintainer, that allowed
> it, then it might happen.  But that would usually be discovered rather
> quickly.
>
> -- Steve
>
>   

Thanks for your reply Steve. I've thought it would be discovered but 
thought I'd ask the question anyway just to make sure. But - do you 
think if OS-X or Windows had a government hack that it would be 
discovered. I know it would be discovered as easilly, but I wonder if 
that would get noticed?


  reply	other threads:[~2006-05-16 13:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 13:24 Wiretapping Linux? Marc Perkel
2006-05-16 13:48 ` Steven Rostedt
2006-05-16 13:56   ` Marc Perkel [this message]
2006-05-16 14:40   ` Jakob Oestergaard
2006-05-16 16:14     ` Steven Rostedt
2006-05-16 15:05 ` linux-os (Dick Johnson)
2006-05-16 15:55   ` Lee Revell
2006-05-16 16:12   ` Chase Venters
2006-05-16 20:29     ` Måns Rullgård
2006-05-16 20:47       ` Chase Venters
2006-05-18 11:25         ` Helge Hafting
     [not found]           ` <Pine.LNX.4.61.0605180741350.4006@chaos.analogic.com>
2006-05-18 12:41             ` Helge Hafting
2006-05-18 15:29               ` Jan Engelhardt
2006-05-16 17:09   ` Ingo Oeser
2006-05-16 17:27     ` Chase Venters
2006-05-17  0:57     ` Peter Chubb
2006-05-16 20:03 ` Willy Tarreau
2006-05-16 21:01   ` Måns Rullgård
2006-05-17  4:21     ` Willy Tarreau
2006-05-17  1:27 ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2006-05-17  8:07 Joerg Pommnitz
2006-05-17 10:24 ` linux-os (Dick Johnson)
2006-05-17 12:02   ` Joerg Pommnitz
2006-05-17 12:16     ` Avi Kivity
2006-05-17 13:25       ` Joerg Pommnitz
2006-05-17 14:17         ` Avi Kivity
2006-05-17 18:47           ` Jan Engelhardt

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=4469D9F5.9030702@perkel.com \
    --to=marc@perkel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 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.