Date: Tue, 25 Jan 2005 10:44:33 -0600
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: Access Control for PYGopherd
Message-ID: <20050125164433.GA25243@excelhustler.com>
References: <41f1b949.YFEnqpZqe2mIe5l9%beaker@freeshell.org>
 <41f665db.1PeT8gwxJFKKuUJ9%beaker@freeshell.org>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41f665db.1PeT8gwxJFKKuUJ9%beaker@freeshell.org>
User-Agent: Mutt/1.5.6+20040907i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Tue, Jan 25, 2005 at 07:29:31AM -0800, Jeff_W wrote:
> > appear to be the built-in access controls found in the UMN Gopherd
> > (not that I ever tried those, but I did notice they were there).
> > Is there a relatively easy way to "wrap" PYGopherd so I can control
> > via TCP Wrappers or do I need to look at firewall stuff like IP
> > Filter, etc. ?
> 
> Hum - is no one else concerned about host access control (for
> pygopherd), or is there just no way to do it outside of a firewall?

Sorry, your message fell behind the quantum mailbox time threshold and
I didn't get to it yet :-)

Anyway, PyGopherd doesn't presently have these features built-in.  It
wouldn't be hard to add them, but you can achieve the same functionality
with Linux ipchains support.

Also, if your machine has two or more network intefaces, you can bind to
only one, meaning that pygopherd will only receive and answer requests
that come in from that network card.  See the "interface" option in
pygopherd.conf.

-- John