fmII
Sun, Jul 27th home | browse | articles | contact | chat | submit | faq | newsletter | about | stats | scoop 02:01 UTC
in
Section
login «
register «
recover password «
[Project] add release | add branch | add screenshot | broken links | change owner | email subscribers | update project | update branch (urls) [Project]

 Driftnet - Default branch
Section: Unix

 

Added: Mon, Jul 16th 2001 06:33 UTC (7 years, 0 months ago) Updated: Wed, Jan 21st 2004 10:30 UTC (4 years, 6 months ago)


Screenshot About:
Inspired by EtherPEG, Driftnet is a program which listens to network traffic and picks out images from TCP streams it observes. It is interesting to run it on a host which sees a lot of web traffic.

Author:
Chris Lightfoot <chris (at) ex (dash) parrot (dot) com> [contact developer]

Rating:
8.39/10.00 (14 votes)

Homepage:
http://www.ex-parrot.com/~chris/driftnet/
Tar/GZ:
http://www.ex-parrot.com/~chris/driftnet/driftnet-0.1.6.tar.gz
Changelog:
http://www.ex-parrot.com/~chris/driftnet/CHANGES
Debian package:
http://packages.debian.org/driftnet

Trove categories: [change]
[Development Status]  3 - Alpha
[Environment]  X11 Applications
[License]  OSI Approved :: GNU General Public License (GPL)
[Operating System]  POSIX :: Linux
[Programming Language]  C
[Topic]  Games/Entertainment, Multimedia :: Graphics :: Capture

Dependencies: [change]
No dependencies filed

 
Project admins: [change]
» Chris Lightfoot (Owner)

» Rating: 8.39/10.00 (Rank N/A)
» Vitality: 0.00% (Rank 13602)
» Popularity: 4.21% (Rank 911)

project statsdownload stats
(click to enlarge graphs)
   Record hits: 67,698
   URL hits: 28,417
   Subscribers: 69

Other projects from the same categories:
Barrage
Wolfenstein: Enemy Territory Statistics
GnomeMemoryBlocks
Blackjack For The Hopelessly Luckless
Pathogen Warrior

Users who subscribed to this project also subscribed to:
XOOPS
StatCVS
QDBM: Quick DataBase Manager
Cyrus IMAP Server
Usermin


Add comment · Rate this project · Subscribe to new releases · Ignore this project · Email this project to a friend · Project record in XML

 Branches

Branch Version Last release License URLs
Default 0.1.6 09-Jul-2002 GNU General Public License (GPL) Homepage Tar/GZ Changelog

 Comments

[»] PNGs?
by Ben Hardy - Sep 18th 2006 00:27:25

It would appear that Driftnet (in its current version anyway) doesn't support the capture and display of PNG images, either that or something in my build died (i don'tthink so because everything else is working fine).

Any chance of a PNG fix? Great software otherwise, scary and cool at the same time :D

[reply] [top]


    [»] Re: PNGs?
    by Arch4Ever - Mar 19th 2008 14:42:59


    > It would appear that Driftnet (in its

    > current version anyway) doesn't support

    > the capture and display of PNG images,


    This is on the todo list (among many other items), but it seems development on this project has ceased. :(

    It would be really cool if someone would continue work on this project.

    [reply] [top]


[»] Thanks
by Niosop - Mar 4th 2004 11:34:15

Just wanted to say thanks for releasing driftnet.
It's great. Part of my job entails monitoring
computer usage to ensure our policies are being
complied with. Driftnet helps a lot.

Also, thanks for coding it so clearly. It would have
been a nightmare adding IP logging if it wasn't so
nicely done.

Thanks again,
Niosop

[reply] [top]


[»] I wish it displayed like etherPEG
by PacketCollision - Apr 28th 2003 21:42:36

I really like the way that etherPEG writes newer pictures in random places, over the older ones, providing a constantly changing tapestry (so to speak) that shows current image viewing trends. Having an option to display in a similar way, rather than the default scrolling method would be very cool.

--
Urge to destroy world rising! -Dark Mage

[reply] [top]


[»] Pretty Cool
by Alex Griffiths - Jun 27th 2002 11:51:36

Thanks Chris, it took a few Makefile changes to get it to work under FreeBSD, but after a couple of minutes it runs fine.

A few suggestions for later releases:

It would be nice to have an option to tag the images with the source and destination IP addresses, yeah I know that would be a pain.

Once the driftnet window is full it redraws everything as it scrolls up; this is awfully slow, how about having a scroll bar instead?

Make sure you insert that "special" tri-lateral commision logo every 42nd image :).

Cheers,
--alex

--
-- Alex Griffiths

[reply] [top]


    [»] Re: Pretty Cool
    by Chris Lightfoot - Jun 27th 2002 11:56:51


    > It would be nice to have an option to
    > tag the images with the source and
    > destination IP addresses, yeah I know
    > that would be a pain.

    It very deliberately doesn't do this. Feel free to add this yourself,
    but I won't accept such a patch into the distribution.

    [reply] [top]


      [»] Re: Pretty Cool
      by Void Main - Sep 29th 2004 21:06:17


      >

      > % It would be nice to have an option to

      > % tag the images with the source and

      > % destination IP addresses, yeah I know

      > % that would be a pain.

      >

      >

      > It very deliberately doesn't do this.

      > Feel free to add this yourself,

      > but I won't accept such a patch into the

      > distribution.

      I actually have a need for this as well, but not for the Big Brother reasons you were probably thinking in your quote above. I spent some time trying to hack out just the parts of driftnet that I needed today but it hasn't been quite as easy as I had hoped.

      I am interested in just grabbing the JPEG images off the wire, checking them for the JPEG buffer overflow vulnerability. If they are infected, log the source and destination address, and URL/image name if possible, but that can be obtained via other means. I actually can take a stock driftnet and use the "-a -m 1000 -d /myjpgs" params and pipe the output to a simple little Perl script that will check the JPEG file for the buffer overflow vulnerability and successfully detect infected JPEGS but it doesn't do me a lot of good without knowing where it came from and where it was going.

      I would like to just get rid of the Perl part and strip out the JPEG grabber from driftnet and check for the vulnerability in memory and only write out the infected files along with the addresses (high utulization circuit). I know if I keep plucking at it I could hack out what I need but if anyone would be interested in helping I could use it.

      You can find the simple details on how to check for the overflow here:

      http://www.easynews.com/virus.html

      If anyone is interested in helping create a tool for this using driftnet (or something more appropriate) let me know. Here's a good place to post:
      http://voidmain.is-a-geek.net/forums/

      I know this wasn't the intended purpose for driftnet but it has most of the parts needed for this needed security app.

      Thanks!

      --
      Void

      [reply] [top]


[»] driftnet->screensaver
by nic0 - May 16th 2002 10:48:11

Don't know how you might rate this idea, but I put it to you as a thought - A small discussion on Slashdot about the possibility of adding screensaver functionality to the project. As kipple mentions, maybe adding the ability to write out the images to enable a screensaver app to pick them up would be an easy route. I'll be honest, I've not thought this out, or looked at driftnet in any detail, but i love the concept - a friend said they have been pondering slapping it on their plasma screen at work as a high tech lava-lamp kinda thing. Good to stare at :)

[reply] [top]


[»] this is the best graphical viewer (combined with http://www.linuks.mine.nu/%70orn-get)
by Gürkan - Sep 28th 2001 11:45:02

what could i say? it was exactly what i was looking for use
together with this script:
http://www.linuks.mine.nu/%70orn-get

[reply] [top]


[»] Reasons for writing such a software
by Hans - Jul 20th 2001 14:01:02

Hello,

I wonder why this software was written?

What is its intended purpose?

First, You might be able to see what kind of websites Your users are watching and You can influence Your users.

"As You can see here, a lot of bandwith is wasted for banners, dirty stuff..."

On the other hand, someone could misuse this tool for spying out the habits of the users.

IMHO a lot more people will use this tool for spying than for sensible purposes because You could also see in Your proxy-logs, what kind of sites are visited.

Therefore, I think it was not a good idea to publish it, what do You think?

[reply] [top]


    [»] Re: Reasons for writing such a software
    by Chris Lightfoot - Jul 22nd 2001 20:03:47


    > Hello,
    >
    > I wonder why this software was
    > written?
    >
    > What is its intended purpose?

    I don't see why you think that it's tremendously subversive or dangerous. It's not a password sniffer, after all. (I would balk at publishing a password sniffer here, on the basis that such a thing is too trivial to be worth publicising; such sniffers are not quite `my first perl script', but they're not much more complex than that.)

    Given that another piece of software already exists that does roughly what Driftnet does (EtherPEG), I can't see that civilisation is going to come crumbling down around our ears simply because random people are now able to extract image data from insecure networks. Unless, of course, you believe that it's OK to give Mac users this technology, but not users of Unix-ish operating systems.

    And, as they say (endlessly, on Slashdot, I believe), you can always encrypt. The rest of us have better ways to spend our time, of course.

    [...]


    > Therefore, I think it was not a good
    > idea to publish it, what do You think?

    Well, not the same as you, obviously.

    [reply] [top]


      [»] Re: Reasons for writing such a software
      by shomon - Jul 31st 2001 03:34:10

      Regardless of wether or not the tool in itself is good or bad, here we're talking to the creator of the tool, as if you could go to an ironmonger to ask if a weapon should really be made. Sure, the developer takes some of the responsibility, specifically the legal issues, and in an open source project, the lead developer can also become or create a hub collecting ideas and patches from other developers involved in the project.

      But it's up to anyone aware of this and other tools which in some circumstances can be applied with groundbreaking capacity, to use the tool in the best possible way. I mean you. As creatively, constructively as possible. Sure, the image of the shady little sysadmin lurking in the dark with other people's jpegs is one of the first to appear in one's mind upon reading about this program and it's capabilities. But there is another image that occurs.

      There is also the image of an environment with a large screen showing all information, shared by everyone, a place with no secrets. Could such a place exist? Maybe the large screen is overkill and such things should be dealt with in a person to person way, revealing our secrets first to those best concerned, or dealing with things ourselves before sharing them, but it's true that we've developed a culture where information is kept hidden. Information is now becoming a jealously guarded secret, something to be owned, that gives power and wealth to those who hold it and the "screen that knows all" might be a good kick in the arse into motion.

      I would ask this developer to keep working, and inspiring people to use his tools, even if it's just so people can snoop other people's jpegs. Whatever. The potential best use is always within our grasp. The hard part is taking the appropriate action.

      --ale@nin.cx

      [reply] [top]


        [»] Re: Reasons for writing such a software
        by Christian Vogel - Apr 11th 2004 11:43:22


        > There is also the image of an

        > environment with a large screen showing

        > all information, shared by everyone, a

        > place with no secrets. Could such a

        > place exist?

        I think at one of the last CCC congresses there was a public
        screen showing sniffed cleartext-passswords for everyone to
        view.... Better encrypt!

        [reply] [top]


    [»] Re: Reasons for writing such a software
    by Ben - Dec 22nd 2002 16:26:21


    > Hello,
    >
    > I wonder why this software was written?
    >
    > What is its intended purpose?
    >
    > [clippage]
    >
    > Therefore, I think it was not a good
    > idea to publish it, what do You think?

    I manage multiple websites, all of which are directly controlled by my company. This software gives an immediate visual indication of what is being viewed, right now, on the site. This (among other things), used in conjunction with another tool that I wrote which dumps currently visited URLs in realtime in a neighboring window, has enabled me to visually spot deep-linked images that are being lifted from our sites (the page holding the image was not fetched); that's going to lead in turn to a controlled response to that unauthorized use of our bandwidth which we are paying for, for our own specific purposes. This benefits our company in a very reasonable and legitmate manner, saving our bandwidth for our legitimate visitors, and in no way invades anyone's privacy. These are our images, after all. And our bandwidth.

    So there are perfectly legitimate uses of the software, and in fact, that was the first thing that occurred to me when I learned of it.

    You know that old saw, "guns don't shoot people, people shoot people"? That applies everywhere. This is just a tool. You can use it neutrally, defensively, or offensively. If there is blame to be laid, lay it at the feet of the user who uses it offensively. Not at the feet of the designer.

    One last thing; you mentioned that you can see what images are being surfed in the server logs. Yes. That's right, you can. Furthermore, you can see the IP that was surfing them. In point of fact, that is much more invasive than driftnet is, because not only do you have a link to the actual station doing the surfing, and hence some accountability, but you also have the ability to parse the logs with a program, sorting out images and users, deriving correlations and hence characterizing the station use. Driftnet provides none of that type of correlating functionality.

    My take is that your position is therefore unsupportable - and inconsequential.

    Ben

    [reply] [top]


      [»] Re: Reasons for writing such a software
      by Hans - Dec 23rd 2002 07:26:49


      > My take is that your position is
      > therefore unsupportable - and
      > inconsequential.
      >

      Hi Ben,

      when I reconsidered my posting then two thinks
      come to my mind:

      First, You are right. Every kind of software gets
      written. To publish it on freshmeat is probably the
      best way to ensure that it will be used in a right
      way. Therefore, I regret my posting and I have
      already sent an excuse to the author.

      Second, my posting is just as wrong as the reaction
      on http://www.ex-parrot.com/~chris/driftnet/.
      As You may have guessed, English is not my first
      language. Therefore, I was more offensive than I
      wanted to be. By asking "I wonder why such software was written"
      I was actually looking for answers
      and did not mean to blame the author.

      Kind regards,

      Hans

      [reply] [top]




© Copyright 2008 SourceForge, Inc., All Rights Reserved.
About freshmeat.net •  Privacy Statement •  Terms of Use •  Trademark Guidelines •  Advertise •  Contact Us • 
ThinkGeek •  Slashdot  •  Linux.com •  SourceForge.net  •  Jobs