public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: "John T. Williams" <jtwilliams@vt.edu>
To: linux-newbie@vger.kernel.org
Subject: Re: filtering .mp3 packets
Date: Wed, 27 Apr 2005 18:57:03 -0400	[thread overview]
Message-ID: <001a01c54b7c$6da1b7f0$660aa8c0@descartes2> (raw)
In-Reply-To: Pine.LNX.4.21.0504272136300.1172-100000@hestia

I don't know mp3 format, but surely they all have a header that is
identifiable?  I mean where they store information about the mp3 such as
speed and title and such.  Surely you could id an mp3 from that information.
and terminate the stream.


----- Original Message ----- 
From: "J." <mailing-lists@xs4all.nl>
To: <linux-newbie@vger.kernel.org>
Sent: Wednesday, April 27, 2005 3:51 PM
Subject: Re: filtering .mp3 packets


> On Wed, 27 Apr 2005, simon wrote:
> > hello Bill
> >
> > >>We've been having some difficulty finding the vocabulary to describe
> > >>filtering content (for example .mp3 files) over TCP-IP. We would like
to
> > >>set up our Linux server to do some "trapping" of packets containing
.mp3
> > >>files with an eye toward using Linux enabled routing to clean our
campus
> > >>of an overwhelming dose of music downloads and trading. To do this
> > >>exploration, I need to know what I should call the process I'm trying
to
> > >>perform. Any vocabulary that you can suggest?
> > >>
> > >>Bill Stanard
> >
> > may be you can write a kernel module using the netfilter to perform
that...
> > netfilter is a very powerful way to build every kind of filter.
> > you can find some informations here :
> > http://www.ouah.org/p61-0x0d_Hacking_the_Linux_Kernel_Network_Stack.txt
> >
> > regards
> >
> > simon
> Wednesday, April 27 21:36:30
>
> Problem is not catching the actual TCP packets, but classifying them like:
> This TCP packet is 100% sure, a packet that contains a piece of mp3 data .
>
> Try to encode a mp3 file, split it into very tiny chunks, remove all but
> one, and see if you can guess if it's a mp3 file..
>
> There is also encryption to deal with, terrible implemented TCP stacks in
> cheap modems and routers when trying to reassemble a whole stream,
> disecting, guessing different protocols and levels.. It's definitively
> a challenge so to speak..
>
> J.
>
> -- 
> Don't worry Ma'am. We're university students, - we know what we're doing.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-04-27 22:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 11:27 filtering .mp3 packets William Stanard
2005-04-25 16:56 ` Ray Olszewski
2005-04-26 11:36 ` John T. Williams
2005-04-27 14:15   ` J.
2005-04-27 15:22     ` simon
2005-04-27 19:51       ` J.
2005-04-27 22:57         ` John T. Williams [this message]
2005-04-28  0:39           ` Ray Olszewski
2005-04-29  3:05             ` joy merwin monteiro
2005-04-29 11:43               ` Stephen Ray
2005-04-29 15:24                 ` joy merwin monteiro
2005-04-29 15:51                   ` Ray Olszewski
2005-04-29 23:39                     ` joy merwin monteiro

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='001a01c54b7c$6da1b7f0$660aa8c0@descartes2' \
    --to=jtwilliams@vt.edu \
    --cc=linux-newbie@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