Date: Sun, 16 Jan 2005 21:55:32 -0600
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: UMN gopherd not logging w/ "-I"
Message-ID: <20050117035532.GC3926@katherina.lan.complete.org>
References: <41eb31b8.cZS6OLmk/RfoiUy1%beaker@freeshell.org>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41eb31b8.cZS6OLmk/RfoiUy1%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 Sun, Jan 16, 2005 at 07:32:08PM -0800, Jeff_W wrote:
> I know this thing is considered obsolete but ...

Worse than that, there are many known security holes in UMN gopherd,
and the expectation is that there are plenty that remain
undiscovered.  For that reason, everyone is strongly encouraged to
cease use of UMN gopherd immediately.

I have developed PyGopherd to be a plug-in replacement for UMN
gopherd.  Its configuration file is different, but it can be set to
understand a complete UMN directory structure.

That's why I have done what I can to officially deprecate UMN gopherd
(I have removed it from my UMN gopher source tree).

So the real answer is: I don't know because I've deleted the code for
my own safety :-)

(Yes, the code is still archived on my server, but really, you should
definately not be running it.)

PyGopherd can, FWIW, log via syslog or to a file, and they do work.

-- John