public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: iptables example on Gentoo
Date: Thu, 8 Sep 2005 18:35:03 +0100	[thread overview]
Message-ID: <20050908183503.45c7e128@hactar.digimed.co.uk> (raw)
In-Reply-To: <loom.20050908T175508-367@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

On Thu, 8 Sep 2005 16:19:53 +0000 (UTC), James wrote:

> > By picking up a bunch of rules from some web site somewhere, you run
> > the risk of learning from bad rules (like learning HTML by picking
> > apart web sites). If a well known and well used program like
> > Shorewall generated bad rules, they'd be picked up immediately.
> 
> Looking at bad rules, learning why they fail, and watching an attack
> (either generated by myself or others) with an IDS and other tools
> running can be an excellent learning experience.

Only if you know they are bad rules. Bearing in mind that you are
unlikely to find a site that says "here are my iptables rules, aren't
they crap?", how will you know whether you are learning from good or bad
examples?


-- 
Neil Bothwick

What Aussies lack in Humour they make up for in Beer!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-09-08 17:43 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 17:22 [gentoo-user] iptables example on Gentoo James
2005-09-06 17:39 ` Dave Nebinger
2005-09-06 17:53   ` Holly Bostick
2005-09-06 18:25     ` [gentoo-user] " James
2005-09-06 19:04       ` Dave Nebinger
2005-09-06 20:00         ` James
2005-09-06 20:39           ` Dave Nebinger
2005-09-07  0:02         ` gentuxx
2005-09-07  1:20           ` W.Kenworthy
2005-09-07 13:08           ` Dave Nebinger
2005-09-07 17:06             ` James
2005-09-07 18:14               ` Holly Bostick
2005-09-07 19:11                 ` James
2005-09-07 19:53                   ` Dave Nebinger
2005-09-08 18:14                     ` James
2005-09-08 19:30                       ` kashani
2005-09-07 20:09                   ` Holly Bostick
2005-09-07 18:40               ` gentuxx
2005-09-07 19:29                 ` James
2005-09-07 19:56                   ` gentuxx
2005-09-07 20:49                     ` Dave Nebinger
2005-09-07 18:48               ` Dave Nebinger
2005-09-07 22:08                 ` James
2005-09-07 23:51                   ` gentuxx
2005-09-08  1:23                     ` James
2005-09-08  9:20                       ` Neil Bothwick
2005-09-08 17:43                         ` James
2005-09-08 16:19                           ` James
2005-09-08 16:42                           ` Dave Nebinger
2005-09-09  9:44                             ` Michael Kintzios
2005-09-09 13:38                               ` Dave Nebinger
2005-09-08 17:35                           ` Neil Bothwick [this message]
2005-09-09  0:52                       ` Jerry McBride
2005-09-07 23:52               ` Rumen Yotov
2005-09-07 18:48                 ` James
2005-09-07 19:44   ` [gentoo-user] " Bryan Whitehead
2005-09-08  1:34     ` [gentoo-user] " James
2005-09-08 15:37       ` Rumen Yotov
2005-09-09 11:19   ` [gentoo-user] " Timo Boettcher
2005-09-09 14:23     ` Dave Nebinger
2005-09-10 17:04       ` Timo Boettcher

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=20050908183503.45c7e128@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.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