From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Chase Venters <chase.venters@clientec.com>
Cc: "Måns Rullgård" <mru@inprovide.com>, linux-kernel@vger.kernel.org
Subject: Re: Wiretapping Linux?
Date: Thu, 18 May 2006 13:25:44 +0200 [thread overview]
Message-ID: <446C59B8.1060402@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.64.0605161541390.32181@turbotaz.ourhouse>
Chase Venters wrote:
>
> Yeah, so to wrap this malware conversation up -- the most effective
> way to implant malicious code in Linux is to crack into developer
> machines and sneak the changes in.
>
> And hope that someone doesn't notice.
The maintainer will. Over and over, we see maintainers tell developers
to fix their patch - often the problem is something as small as
"bad withespace" or "stupid name for a variable".
Now try to get a backdoor in, and see the maintainer get a fit over
the changes that are clearly unrelated to the problem mentioned
in the changelog.
And if you succeed with the spyware anyway, then someone will notice
the strange packets going out. That you cannot prevent, and it will then
be tracked down. Or you get a backdoor in? It will be found as soon as
it sees some use, or likely earlier with all the more or less automated
vulnerability chacking going on.
Helge Haftinjg
next prev parent reply other threads:[~2006-05-18 11:28 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
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 [this message]
[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=446C59B8.1060402@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@inprovide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox