Received: with ECARTIS (v1.0.0; list gopher); Fri, 21 Jan 2005 20:24:49 -0600 (CST) Received: from mx.freeshell.org ([192.94.73.21] helo=sdf.lonestar.org) by glockenspiel.complete.org with esmtp (Exim 4.34) id 1CsAxA-000740-VK for gopher@complete.org; Fri, 21 Jan 2005 20:24:48 -0600 Received: from sdf.lonestar.org (IDENT:beaker@otaku.freeshell.org [192.94.73.2]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id j0M2O99n014840 for <gopher@complete.org>; Sat, 22 Jan 2005 02:24:10 GMT Received: (from beaker@localhost) by sdf.lonestar.org (8.12.10/8.12.8/Submit) id j0M2O9Ik002684 for gopher@complete.org; Fri, 21 Jan 2005 18:24:09 -0800 (PST) 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 X-Spam-Status: No (score 0.3): NO_REAL_NAME=0.285 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Fri, 21 Jan 2005 20:24:48 -0600 X-archive-position: 1008 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: beaker@freeshell.org Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

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