Complete.Org: Mailing Lists: Archives: gopher: January 2005:
[gopher] Re: Access Control for PYGopherd
Home

[gopher] Re: Access Control for PYGopherd

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Access Control for PYGopherd
From: Jeff_W<beaker@xxxxxxxxxxxxx>
Date: Tue, 25 Jan 2005 07:29:31 -0800
Reply-to: gopher@xxxxxxxxxxxx

Jeff_W<beaker@xxxxxxxxxxxxx> wrote:

> 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. ?

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?

-Jeff



[Prev in Thread] Current Thread [Next in Thread]