From: SBlaze <dagent.geo@yahoo.com>
To: Jean-Rene Cormier <jean-rene.cormier@cipanb.ca>
Cc: netfilter@lists.netfilter.org
Subject: Re: Blocking Kazaa
Date: Fri, 22 Aug 2003 11:38:48 -0700 (PDT) [thread overview]
Message-ID: <20030822183848.21628.qmail@web40206.mail.yahoo.com> (raw)
In-Reply-To: <1061573560.17418.27.camel@forbidden.cipanb.ca>
http://www.securitymetrics.com/portscan.adp
Above is an online port scanner. It scans for Kazzaa openings(among other
things). It seems to think that Kazzaa is open always on 1214. As I said before
I am not sure as I do not use Kazzaa. If you find anything out about this I
will gladly write up something on my web site to show other users how to block
Kazzaa as it seems to come up alot.
Thanks
SBlaze
--- Jean-Rene Cormier <jean-rene.cormier@cipanb.ca> wrote:
> I haven't checked the source ports but I doubt after all they did to get
> around firewalls that they would put fixed source ports. Though I'll
> check it out, you never know.
>
> Jean-Rene Cormier
>
>
> On Fri, 2003-08-22 at 14:23, SBlaze wrote:
> > I don't know much about Kazzaa I never used it...but you said you checked
> the
> > connection ports right? What about source ports. Check both the source and
> the
> > destination port(s) and see if you see any consistencies. Sometimes you
> don't
> > need to block ALL ports just the ones that initiate a connection.
> >
> > Hope this helps
> > SBlaze
> >
> > --- Jean-Rene Cormier <jean-rene.cormier@cipanb.ca> wrote:
> > > Anybody know a way of blocking Kazaa? I've tried the string matching way
> > > but it doesn't seem to work. I tried logging all connections from my
> > > windows desktop so I could see to which port it connects and it connects
> > > to so many different port that you basically need to block ports 1000 to
> > > 4000 but after that it connects to port 80 which obviously I can't
> > > block. I installed ethereal on the windows desktop to check which string
> > > I could filter but couldn't find anything useful.
> > >
> > > Anybody have an idea what can be done? I'm thinking another option would
> > > be to block the IP of the servers but there seem to be quite a list...
> > > that's if it doesn't just try some random IPs...
> > >
> > > Jean-Rene Cormier
> > >
> > >
> >
> >
> > =====
> > "Winky is not knowing how sir, winky is not knowing how?" -=Winky / Harry
> Potter and the Goblet of Fire=-"
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! SiteBuilder - Free, easy-to-use web site design software
> > http://sitebuilder.yahoo.com
>
=====
"Winky is not knowing how sir, winky is not knowing how?" -=Winky / Harry Potter and the Goblet of Fire=-"
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
next prev parent reply other threads:[~2003-08-22 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 11:49 Blocking Kazaa Jean-Rene Cormier
2003-08-22 17:23 ` SBlaze
2003-08-22 17:32 ` Jean-Rene Cormier
2003-08-22 18:38 ` SBlaze [this message]
2003-08-24 0:01 ` Stephen Smoogen
-- strict thread matches above, loose matches on Subject: below --
2003-08-24 1:47 George Vieira
2003-08-29 21:12 ` Stephen J. McCracken
2002-11-19 16:11 blocking kazaa Fadel
2002-11-26 1:33 ` George J. Jahchan, Eng.
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=20030822183848.21628.qmail@web40206.mail.yahoo.com \
--to=dagent.geo@yahoo.com \
--cc=jean-rene.cormier@cipanb.ca \
--cc=netfilter@lists.netfilter.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