From owner-freebsd-questions@FreeBSD.ORG  Sat Aug 16 08:53:06 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F305737B401
	for <freebsd-questions@freebsd.org>;
	Sat, 16 Aug 2003 08:53:05 -0700 (PDT)
Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 28A0244A18
	for <freebsd-questions@freebsd.org>;
	Sat, 16 Aug 2003 08:53:05 -0700 (PDT)
	(envelope-from freebsd-questions-local@be-well.no-ip.com)
Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37])
          by comcast.net (sccrmhc13) with ESMTP
          id <2003081615530301600alcc5e>; Sat, 16 Aug 2003 15:53:03 +0000
Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37]
	(may be forged))
	by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h7GFr3Me056993
	for <freebsd-questions@freebsd.org>;
	Sat, 16 Aug 2003 11:53:03 -0400 (EDT)
	(envelope-from freebsd-questions-local@be-well.no-ip.com)
Received: (from lowell@localhost)
	by be-well.ilk.org (8.12.9/8.12.6/Submit) id h7GFr2nM056990;
	Sat, 16 Aug 2003 11:53:02 -0400 (EDT)
X-Authentication-Warning: be-well.ilk.org: lowell set sender to
	freebsd-questions-local@be-well.ilk.org using -f
Sender: lowell@be-well.no-ip.com
To: freebsd-questions@freebsd.org
References: <000301c363a1$11eec110$04fea8c0@moe>
From: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com>
Date: 16 Aug 2003 11:53:02 -0400
In-Reply-To: <000301c363a1$11eec110$04fea8c0@moe>
Message-ID: <44ada9oazl.fsf@be-well.ilk.org>
Lines: 24
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: Make popa3d listen on specific interface
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Aug 2003 15:53:06 -0000

"Charles Howse" <chowse@charter.net> writes:

> Let me throw this in:
> This is a home network, behind a Cable Modem and 4-port Cable/DSL router
> w/ firewall.
> Port 110 is closed on the firewall.  Ports 80,20 and 21 are open on
> another machine in the DMZ.
> That said ( and I'm no expert ) wouldn't it be acceptable for *my*
> situation to bind to an address?
> That way, anyone wanting to crack into the pop server on this machine
> would have to get past the firewall, and then discover the address the
> pop server on this machine is listening on...? Nmap woud certainly do
> that, *if* they got in.
> I run a pop server on the Redhat machine next to the FreeBSD machine, no
> problems ever there.
> I could be way off on my logic, and my understanding of tcp/ip, so
> correct me if I'm wrong.

Not at all; you're dead on.  
The only thing I'm trying to warn you about is that binding to a
specific address is having a fairly small effect on your security in
this case.  For belt-and-suspenders protection, you'd be somewhat 
better off with a more sophisticated POP server which can bind to 
the inside interface directly instead of just the address.