From: Joel Newkirk <netfilter@newkirk.us>
To: Nimit Gupta <nimit@deeproot.co.in>
Cc: "inghau@perkom.co.id" <inghau@perkom.co.id>,
"netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: how to block kazaa ?
Date: Wed, 26 Feb 2003 02:00:37 -0500 [thread overview]
Message-ID: <200302260200.37822.netfilter@newkirk.us> (raw)
In-Reply-To: <Pine.LNX.4.43.0302261032380.375-100000@debian.lan.deeproot.co.in>
On Wednesday 26 February 2003 12:07 am, Nimit Gupta wrote:
> hello,
> Just going thru the thread so that i could learn form others
> problem. One thing I could not understand is, how to custom compile a
> kazaa-blocking kernel?
Sorry, what I was referring to was using Patch-O-Matic to add newer
features to netfilter, like the string match and Arnt Karlsen's favored
TARPIT target, and then recompiling the kernel to incorporate the
patches. It's not really a 'kazaa-blocking' kernel, just in this case
one compiled especially because of the desire to block kazaa.
j
> > But newer implementations apparently support port-hopping, so it
> > seems that the only confirmed way to stop it with iptables is with
> > the STRING match from patch-o-matic, and block anything with the
> > string "kazaa" (don't recall case requirements) in it. Compiling a
> > custom kazaa-blocking kernel may be more than you want to do,
> > though.
>
> Thanks a lot.
>
> with regards,
> Nimit.
next prev parent reply other threads:[~2003-02-26 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 2:44 how to block kazaa ? inghau
2003-02-26 3:42 ` Joel Newkirk
2003-02-26 5:07 ` Nimit Gupta
2003-02-26 7:00 ` Joel Newkirk [this message]
2003-02-26 7:21 ` hare ram
2003-02-26 5:28 ` Scott Lamb
2003-02-26 4:20 ` Arnt Karlsen
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 6:07 Joel Newkirk
2003-02-26 6:41 lawrence Of Arabia
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=200302260200.37822.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=inghau@perkom.co.id \
--cc=netfilter@lists.netfilter.org \
--cc=nimit@deeproot.co.in \
/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