All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IP2P & Skype question
Date: Wed, 27 Apr 2005 04:29:19 +0000	[thread overview]
Message-ID: <426F151F.69CBE9E3@iswest.com> (raw)
In-Reply-To: <426CEBC7.9050505@pbltd.net>

Andy Furniss wrote:
> 
> Taylor, Grant wrote:
> >> Regarding yahoo messenger, I have not looked at this for a while. As I
> >> understood, it used a single outgoing port and if blocked - end of
> >> yahoo....  Or has this changed since I last looked?
> >
> >
> > This must have changed as Yahoo will try to connect 4 different servers
> > on 8 different ports for basic IM use.  If you want to use other
> > features like the webcam, file shareing, or voice chat there are
> > different servers and different ports that your client will connect to.
> > Take a look at
> > http://help.yahoo.com/help/us/sbc/messenger/signin/signin-02.html if you
> > want to see Yahoo's definition of what the client does.  I wrote a RegEx
> > of the various host names that Yahoo will connect to,
> > "((scs(|a-z)|filetransfer).msg|v(0-99).(vc|vip).sc(a-z|0-99)|webcam).yahoo.com".
> > If I could implement a match in DNS for this RegEx I would do so to
> > prevent computers on my networks from finding things.
> 
> What fun it must be being a netadmin - what don't you want to block, by
> which I mean wouldn't it be easier to block everything and run
> squid/mail server.
> 
> Andy.

Yes, I too have been reading these things asking myself why one would
allow users such open access.  One reason, of course, is that it is
difficult to allow some http but not other, so if the port is 80, it
pretty much has to be OK.  So how would squid (or anything else except
perhaps Level 7) know that this particular connection is A Bad Thing?

I have been successful at limiting the number of FTP connections per
user using iptables' connlimit and helper.  That's where I'd start.  And
if three turned out to be too many, I'd reduce connlimit to 2 for HTTP
and 1 for FTP.
iptables -N HTTP
iptables -A HTTP -p tcp -m connlimit --connlimit-above 3 -j DROP
iptables -A HTTP -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A HTTP -j RETURN

iptables -A FORWARD -p tcp --dport 80 -j HTTP
iptables -A FORWARD -p tcp --sport 80 -j HTTP
iptables -A FORWARD -m helper --helper ftp -j HTTP

In conjunction with my ACL (posted here a while back; it limits specific
users to specific ports), the above would not be total deny, but it sure
would put a dent in abuse.

gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-04-27  4:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 13:08 [LARTC] IP2P & Skype question Gary Smith
2005-04-25 14:20 ` Andreas Klauer
2005-04-25 14:33 ` Justin Schoeman
2005-04-25 14:57 ` Andreas Klauer
2005-04-25 15:35 ` Gary Smith
2005-04-25 18:22 ` Taylor, Grant
2005-04-26  7:29 ` Michael Renzmann
2005-04-26  7:38 ` Taylor, Grant
2005-04-26 12:52 ` Gary Smith
2005-04-26 22:02 ` Taylor, Grant
2005-04-26 23:11 ` Andy Furniss
2005-04-27  4:29 ` gypsy [this message]
2005-04-27  5:08 ` Taylor, Grant
2005-04-27  5:22 ` Taylor, Grant

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=426F151F.69CBE9E3@iswest.com \
    --to=gypsy@iswest.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.