Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: insecure script
Date: Tue, 23 Mar 2004 20:17:17 +0000	[thread overview]
Message-ID: <200403232017.17094.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040323195832.0ACB83BAD18@smtp.latinmail.com>

On Tuesday 23 March 2004 7:58 pm, Jorge Garcia wrote:

> hi, im starting to write a paper about iptables security, and im trying to
> focus in the scripts. anyone can give some examples of insecure scripts or
> some tips to find my own insecurities in many scripts on the net. how
> hackers can take advantages in insecurities in the scriipts??

Here's a few ideas:

1. Don't use a default ACCEPT policy on INPUT or FORWARD chains.

2. Don't try to "block the bad stuff and allow the rest" - always "allow what 
you know you want, and block the rest"

3. Use stateful matching - don't just allow packets in to high port numbers on 
the basis that "they must be replies"

4. Don't assume that all packets from source port 53 are DNS.

5. Be careful about allowing all connections from internal clients to the 
Internet - somebudy might bring a compomised laptop into your network, or 
somebody inside the organisation might not be trustworthy.   Check for 
suspicious outgoing traffic as well as incoming.

Regards,

Antony.

-- 
If you can't find an Open Source solution for it, then it isn't a real 
problem.

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-03-23 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 19:58 insecure script Jorge Garcia
2004-03-23 20:17 ` Antony Stone [this message]
2004-03-23 20:49   ` Brice GIBOUDEAU
  -- strict thread matches above, loose matches on Subject: below --
2004-03-23 21:40 Daniel Chemko

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=200403232017.17094.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --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