Date: Fri, 21 Jan 2005 18:24:09 -0800
From: =?iso-8859-1?Q?Jeff=5FW?=<beaker@freeshell.org>
To: gopher@complete.org
Subject: [gopher] Access Control for PYGopherd
Message-ID: <41f1b949.YFEnqpZqe2mIe5l9%beaker@freeshell.org>
User-Agent: nail 11.17 11/18/04
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

What is the recommended way to control access to PYGopherd? Looking
through some of the list archives I've gathered that PYG can't be
run via inetd, and it seems TCP Wrappers is mainly for services
run out of inetd (sshd apparently can be controlled by TCP Wrappers
as well even though it isn't in inetd.conf). There also doesn't
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. ?

TIA,
-Jeff