Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Mike Ireton <mike-netfilter@tiedyenetworks.com>
To: "R. DuFresne" <dufresne@sysinfo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Using -m limit to stop outbound portscanning viruses
Date: Sat, 05 Feb 2005 15:06:01 -0800	[thread overview]
Message-ID: <42055159.6000102@tiedyenetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10502051748230.352-100000@darkstar.sysinfo.com>


I'm not, and that's the point. I aim to put a condom on the customer 
side of the link so that they _can't_ engage in this behavior, no matter 
what virus or stealth zombie ddos tool they have been infected with. 
This gets me out of having to play traffic cop and is one more way I 
ensure that the service can't be (easilly) abused.

R. DuFresne wrote:

>Why are you letting this traffic traverse your perimiters in the first
>place?  If there is a need to pass windows related problematic protocols
>across perimiters, they should be tunnels in a secure connection.
>
>
>  
>




  reply	other threads:[~2005-02-05 23:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05 22:37 Using -m limit to stop outbound portscanning viruses Mike Ireton
2005-02-05 22:49 ` R. DuFresne
2005-02-05 23:06   ` Mike Ireton [this message]
2005-02-05 23:51     ` R. DuFresne
2005-02-05 22:50 ` Ramoni

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=42055159.6000102@tiedyenetworks.com \
    --to=mike-netfilter@tiedyenetworks.com \
    --cc=dufresne@sysinfo.com \
    --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