From: Joerg Pommnitz <pommnitz@yahoo.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wiretapping Linux?
Date: Wed, 17 May 2006 14:02:05 +0200 (CEST) [thread overview]
Message-ID: <20060517120205.68976.qmail@web51406.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605170618210.31079@chaos.analogic.com>
--- "linux-os (Dick Johnson)" wrote:
>
> CPUs inside network cards (if any) don't run in the same address-space
> as your host CPU, memory, etc. Data is DMAed (set up on the host-CPU
> side) to/from this private bus, using the PCI bus. You would need
> very extensive cooperative code running on the host CPU (in the
> driver) to do anything useful. If you are going to write such
> driver code, you don't need the CPU inside the controller card
> at all because you are already running with high privileges on
> the correct bus.
Wiretapping is about listening in on communication. Network cards are the
means this communication is carried out and see all the traffic somebody
might want to tap into. This clearly makes it at least theoretically
possible to use them as a listening device (and it sees all the other
traffic on its network segment, too).
Additionally its listening on the system bus. Question: Can it tap into
data addressed to another peripheral (say the hd controller)? If so, then
only the system RAM is outside its scope.
Regards
Joerg
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
next prev parent reply other threads:[~2006-05-17 12:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 8:07 Joerg Pommnitz
2006-05-17 10:24 ` linux-os (Dick Johnson)
2006-05-17 12:02 ` Joerg Pommnitz [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 13:24 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
[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
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=20060517120205.68976.qmail@web51406.mail.yahoo.com \
--to=pommnitz@yahoo.com \
--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®