From: "John T. Williams" <jtwilliams@vt.edu>
To: William Stanard <wstanard@palmertrinity.org>,
linux-newbie@vger.kernel.org
Subject: Re: filtering .mp3 packets
Date: Tue, 26 Apr 2005 07:36:25 -0400 [thread overview]
Message-ID: <001101c54a54$2e0dc5d0$660aa8c0@descartes2> (raw)
In-Reply-To: fc.004c4e00007a2960004c4e00007a2960.7a296f@palmertrinity.org
Bill Stanard,
There are many ways to attack the mp3 problem, but the one you trying for is
probably the most problematic. You would not only need to check packets for
mp3's, but you would also have to understand the various protocols used by
file sharing software. My university tracks the amount of bytes uploaded
by a user and limits bandwidth of users who upload too much. (indicating
that the user is doing something of which the school wouldn't approve).
There are very few uses for massive uploads which would not violate the
average university's Internet use agreement, and those cases could be
addressed on a user by user bases.
However the only way to truly limit the behavior will be to convince the
students not to do it. Otherwise there will always be a work around.
Packet sniffing is questionable ethical and in some states may violate the
rights of the users, however you can probably do ports scans to protect the
network security and find people running servers on ports which are commonly
used for file sharing. If someone is running a publicly open server, I
cannot see any problem with finding out what content is being served. You
could probably write a robot of some sort that could search the file sharing
ports, and raise a flag if it finds contents with *.avi or *.mp3 on it, but
I would check with your legal department before doing so.
----- Original Message -----
From: "William Stanard" <wstanard@palmertrinity.org>
To: <linux-newbie@vger.kernel.org>
Sent: Monday, April 25, 2005 7:27 AM
Subject: filtering .mp3 packets
> 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
> Academic Computing
> Palmer Trinity School
> 305.969.4239
>
>
>
> -
> 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
next prev parent reply other threads:[~2005-04-26 11:36 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 [this message]
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
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='001101c54a54$2e0dc5d0$660aa8c0@descartes2' \
--to=jtwilliams@vt.edu \
--cc=linux-newbie@vger.kernel.org \
--cc=wstanard@palmertrinity.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