public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sean Mitchell <SMitchell@phoenix-interactive.com>
To: gentoo-dev@cvs.gentoo.org
Subject: RE: [gentoo-dev] NAT iptables info
Date: Wed Oct  3 13:53:02 2001	[thread overview]
Message-ID: <1DCB85BD45DED211B12D009027279E4F47700B@murcury> (raw)

> From: Donny Davies [mailto:woodchip@gentoo.org]

> Nope. Sorry. Im not in agreement in this at all. Of course, 
> its open to debate,
> Im not saying I know everything, nor Im 100% right. Go ahead, 
> debate away.
> But I dont want any part of it, Ill tell you that!
> 
> If you dont understand the ramnifications of packet 
> filetering, NAT, etc then
> you have *no* business running this software. We are not 
> Microsoft or Wingate,
> opening yuor machine to a wider world.

<snip rest of post>

I have to agree in principle here, FWIW. The answer to this problem of
making the functionality available to everyone is to make sure things are
clearly and thoroughly documented. I think we are best served by following
the OpenBSD example of a secure default install and then let the users
change configuration to suit.

Cheers,

Sean



             reply	other threads:[~2001-10-03 19:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 13:53 Sean Mitchell [this message]
2001-10-04  4:54 ` [gentoo-dev] NAT iptables info Djamil ESSAISSI
2001-10-04 13:29   ` Daniel Robbins
2001-10-04 14:31     ` Nathaniel Grady
2001-10-05  3:47     ` Djamil ESSAISSI
2001-10-05 10:28       ` Daniel Robbins
  -- strict thread matches above, loose matches on Subject: below --
2001-10-04 14:48 Sherman Boyd
2001-10-03 13:39 Donny Davies
2001-10-03 13:46 ` Michael M Nazaroff
2001-10-03 18:12   ` Collins Richey
2001-10-03 13:15 Sherman Boyd
2001-10-01 15:02 Donny Davies
2001-10-01 20:29 ` Chad Huneycutt
2001-10-02  4:13 ` Djamil ESSAISSI

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=1DCB85BD45DED211B12D009027279E4F47700B@murcury \
    --to=smitchell@phoenix-interactive.com \
    --cc=gentoo-dev@cvs.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