RSG on Fri, 21 Jun 2002 04:24:00 +0200 (CEST)

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: <nettime> How We Made Our Own "Carnivore" [6x]

>From: Andreas Broeckmann <>
>[...] discuss the technical analysis offered by the Moscow-jury which, 
>from what i understand as a techno-idiot and reading against the grain, 
>basically says that your Carnivore program offers nothing new under the sun??

as stated in our original post, Carnivore Personal Edition is rich with
new features not included in its FBI counterpart. Here are a few of

1) artist-made diagnosic clients created by leading net artists around
the world

2) remote access--meaning clients can access CarnivorePE data streams
from other computers via the Internet

3) full subject targetting--meaning all users are sniffed, not just a
single user

4) full data targetting--all data is sniffed, not just email

5) volume buffering--to avoid packet storms, CarnivorePE can buffer
packet output to either 1, 5, 20, or 100 packets per second.

6) transport protocol filtering--meaning CarnivorePE can sniff on TCP or
UDP packets, or both

7) output channels--meaning clients can request one of three output
channels: "carnivore" for full packet data in ASCII, "hexivore" for full
packet data in hex, or "minivore" for packet headers only

8) an open source software license (a dramatic improvement over its
chief rival, Etherpeek, which isn't open source and costs $1,295)

9) a distributed rather than centralized architecture

most of these features are also missing in the various other sniffers
available including Snort and tcpdump.

instead of stumbling over technical details, perhaps the nettime
community can engage in a deeper critique of the software and its uses?


#  distributed via <nettime>: no commercial use without permission
#  <nettime> is a moderated mailing list for net criticism,
#  collaborative text filtering and cultural politics of the nets
#  more info: and "info nettime-l" in the msg body
#  archive: contact: