HDTenEightyP/NetNews huggingface dataset:
From: valke@cca.vu.nl (Peter Valkenburg)
Newsgroups: comp.infosystems.gopher
Subject: Re: cookbook for secure gopher wanted
Date: 14 Aug 92 10:16:05 GMT
Organization: VU Amsterdam - dienst CCA

jqj@duff.uoregon.edu (JQ Johnson) writes:

>I'd like to set up a telnet to gopher gateway by creating a userid on a
>Unix system (in this case SunOS 4.1.2) that runs a secure gopher client. 
..
>My concerns:
..
>   - by default, "gopher -s" allows mailing of downloaded files

Yup.  And the way options are passed to mail is *still* somewhat unsave.
I patched my v1.02 client to disable mail for the secure option (trivial
patch included below).

>   - we believe that good Internet citizenship requires that we not
>     offer unauthenticated telnet to off-campus locations.  However, we
>     do allow unauthenticated telnet to oncampus locations, e.g. the
>     gateway machine

We took a middle road between not allowing any telnets and allowing free
access, by using a patched version that does not allow the user to open
new connections after typing the escape character.  You can use the BSD
telnet (source available on the net) on a Sun -- it can be installed in
the gopher login's home directory.
Needless to say, this scheme relies on Gopher servers to offer sensible
telnet links..

It might be a good idea to disallow any off-campus access to your "free"
gopher client.  In fact, I think we're going to do that ourselves..

Good luck,

	Peter Valkenburg
	Dept. of Computer Affairs
	Vrije Universiteit Amsterdam
	The Netherlands
	Email: valke@cca.vu.nl


--cdiff-included-below--cdiff-included-below--cdiff-included-below--
*** ourutils.c  Wed Aug  5 15:51:09 1992
--- ourutils.c~ Wed Aug  5 15:27:00 1992
***************
*** 115,121 ****
       if (!SecureMode)
          printf(", <m> to mail, 
 to save, or <p> to print:");
       else
!         printf(":");
  
       fflush(stdout);
       noecho();
--- 115,121 ----
       if (!SecureMode)
          printf(", <m> to mail, 
 to save, or <p> to print:");
       else
!         printf(", <m> to mail:");
  
       fflush(stdout);
       noecho();
***************
*** 135,145 ****
               case KEY_ENTER:
               case ' ':
                    break;
-              /* Mail is still unsave (valke@cca.vu.nl)
               case 'm':
                    mail_file(Filename, Realname);
                    break;
-               */
  
               default:
                    puts(CURgetBell(CursesScreen));
--- 135,143 ----
--cdiff-included-above--cdiff-included-above--cdiff-included-above--
Date: Mon, 17 Aug 92 21:16:38 CDT
From: mpm@boombox.micro.umn.edu ("Mark P. McCahill" )
Reply-To: "Mark P. McCahill"  <mpm@boombox.micro.umn.edu>
Original-To: bkc@omnigate.clarkson.edu, gopher@boombox.micro.umn.edu,
        gopher-news@boombox.micro.umn.edu
Subject: Re: Comments about Gopher+
Newsgroups: comp.infosystems.gopher
Distribution: comp

> Brad Clements :
> .. 
> ..   A month ago I suggested that you allow the server to keep the connection
> ..   open if it so desires. I received no reply from that suggestion, 
> ..   not even a reason as to why it wasn't acceptable.

One other problem with the keep-the-connection-open idea: since the gopher 
system is a distributed server architecture, it is really common for a client 
to grab one thing off server A, then something else off server B, then 
something else off server C. Keeping connections open is not a win when the 
client hops over to another server, and the overhead of keeping connections 
open for a long time kills servers. Gopher needs to stay stateless and close 
connections immediately so that it is feasible to do a lot of transactions on 
wimpy little Mac and PC servers. Keep in mind that the gopher design point is 
that people can run servers off desktop machines and there are a lot of 
distributed servers.


Mark P. McCahill      
                                                                
University of Minnesota                      Computer & Information Services
room 125 Shepherd Labs                             mpm@boombox.micro.umn.edu    
100 Union Street SE                                     612 625 1300 (voice)    
Mpls., MN 55455                                           612 625 6817 (fax)
From: blm@glnpogis5.r05.epa.gov
Newsgroups: comp.infosystems.gopher
Subject: Re: Gopher for the Technically Impaired
Date: 14 Aug 92 10:50:04 GMT
Distribution: comp
Original-To: flowney@gcnext.gac.peachnet.edu, gopher-news@boombox.micro.umn.edu



Frank,

I would appreciate such a document.  If you could pass any informationknowing about such a document. If one exits would you
please let me know how to get it.  Thanks

Barry Manne
 312 353-8015
 manne.barry@epamail.epa.gov

 US EPA  Region 5
 Great Lakes Program
 77 W Jackson St
 Chicago, IL  60614
------------------------------
From mail Wed Aug 12 07:52 CDT 1992
Received: from mail.unet.umn.edu by glnpogis5.r05.epa.gov (5.4/5.40/1.0)
	id AA26887; Wed, 12 Aug 1992 07:52:46 -0400
Received: from boombox.micro.umn.edu by mail.unet.umn.edu (5.65c/)
	id AA21568; Wed, 12 Aug 1992 07:24:21 -0500
Received: by boombox.micro.umn.edu; Wed, 12 Aug 92 07:24:43 CDT
Received: by boombox.micro.umn.edu; Wed, 12 Aug 92 07:17:45 CDT
Received: from gcnext.GAC.PeachNet.EDU by boombox.micro.umn.edu; Wed, 12 Aug 92 07:17:37 CDT
Received: from [131.144.54.81] by  gcnext.gac.peachnet.edu  (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
	id AA22174; Wed, 12 Aug 92 08:06:22 EDT
Message-Id: <9208121206.AA22174@ gcnext.gac.peachnet.edu >
Date: Wed, 12 Aug 1992 07:59:07 -0500
To: gopher-news@boombox.micro.umn.edu
From: flowney@gcnext.gac.peachnet.edu
Subject: Gopher for the Technically Impaired
Content-Type: text
Content-Length: 943
Status: RO

Is there a document which lucidly explains the gopher concept as "Zen and
the Art of the Internet" explains the Internet in general?  As a person who
is embarking on the task of convincing holders-of-the-bucks to allocate
funds to an enterprise that will may use the gopher concept, this would
come in mighty handy.  I need lucid and comprehensive descriptions of the
client and server (gophermeister?) perspectives.  Specifically, what are
the possibilities and what are the costs (in hardware, software and wetware
[people]) involved in realizing that potential.
****************************************************************************
flowney@gcnext.gac.peachnet.edu (Frank Lowney), Director
The Regional Teacher Education Center at Georgia College
231 W. Hancock St., Milledgeville, GA  (912) 453-5121
AppleLink: GCEDUNET / GC EduNET: GCEDUNET.PEACHNET.EDU
****************************************************************************
Newsgroups: comp.infosystems.gopher
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: Re: waisindex-ing a gopher directory but avoiding .cap and .cache
Organization: Draper Laboratory
Date: Thu, 13 Aug 1992 13:15:00 GMT

In article <65733@hydra.gatech.EDU>,
ccoprmm@prism.gatech.EDU (Michael Mealling) writes:

>I have a minor annoyance that I was wondering if anyone else has
>circumvented easily. I'm recursively waisindex-ing some files that
>are in my gopher directory. The problem is that waisindex also indexes
>all my .cap and .cache files. Does anyone know of a way around this?
>Thanks...

You could try changing the permissions on the .cap and .cache files
so that gopher, but not wais, can read them.  waisindex will skip
(but not without complaining) files it can't read.

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Newsgroups: comp.infosystems.gopher
Subject: Index Search Server help?
From: pcrayne@odie.santarosa.edu (Pete Crayne)
Date: 12 Aug 92 15:32:05 PDT
Distribution: world
Organization: Santa Rosa Junior College, Santa Rosa, CA

Are there any online documents that provide details on index search servers?
Specifically, I'd like to know how to implement one but I'd be grateful
for just about any available info. The gopher.FAQ was a little skimpy on the
topic.

Since this is probably a FAQ, please reply directly.
TIA.
PETE@CIS.SANTAROSA.EDU
or
PCRAYNE@ODIE.SANTAROSA.EDU
From: daniel@bauhaus (Daniel Torrey)
Subject: Re: will the NeXT users out there please speak ASCII like the rest of us?
Original-To: rodgers@maxwell.mmwb.ucsf.edu (R. P. C. Rodgers, M.D.)
Date: Wed, 12 Aug 92 10:03:19 CDT
Original-Cc: gopher-news@boombox.micro.umn.edu
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: comp.infosystems.gopher
Distribution: comp

R. P. C. Rodgers, M.D. :
. 
. Dear Fellow Gopher List Members,
. 
. It seems a signal discourtesy to me to send out messages such as

 [etc.]

Don't be silly.  NeXTMail is sort of neat if you have a NeXT; no reason that
NeXT users should be harassed for using it.  It might be nice if they'd put
*** NeXTMAIL *** in the subject line, but even if they don't, one can always
just DELETE IT. 

-- 

Daniel A. Torrey                           daniel@bauhaus.micro.umn.edu
University of Minnesota                                  (612) 626-8663
CIS/UAP/ETC               In gopherspace, no one can hear you scream...
Newsgroups: comp.infosystems.gopher
From: jqj@duff.uoregon.edu (JQ Johnson)
Subject: Re: Unix client to auto-load after login: gopher (how?)
Organization: University of Oregon Network Services
Distribution: comp
Date: Sat, 22 Aug 92 00:08:15 GMT

Burrow managers who have set up "gopher" logins (allowing access to
gopher from not-logged-in users) should beware of a security hole:

If you are using the "-s" option to the Unix gopher client, do NOT 
allow mail using the default /usr/ucb/mail GOPHER_MAIL program, since
it allows a cracker to access any file readable by the gopher login
(e.g. /etc/passwd).

I notice that the gopher client on uiuc carefully disallows <m> after
viewing a file.  This is probably the right approach.  If you plan to use
the standard gopher client, I recommend something such as the following as
a semi-secure shell for the gopher login (the version of more and telnet
are the ones from the Gopher_tools.tar file):


#! /bin/sh
# This shell is designed to be run as the login for user "gopher"
# and to provide a secure environment for running gopher from a terminal.
# Note:  the "gopher" user id should have a home directory that is NOT
#	publicly writable, is not owned by "gopher", and does not contain 
#	.profile or similar files

GOPHER_ROOT=/usr/local/gopher-data
PATH=/usr/5bin:/usr/bin export PATH
SHELL=/dev/null export SHELL
PAGER=${GOPHER_ROOT}/bin/more export PAGER
GOPHER_TELNET=${GOPHER_ROOT}/bin/telnet export GOPHER_TELNET
GOPHER_MIME=$PAGER export GOPHER_MIME
GOPHER_PLAY=/dev/null export GOPHER_PLAY
# GOPHER_MAIL="/usr/ucb/mail -r gopher" export GOPHER_MAIL
GOPHER_MAIL=/dev/null export GOPHER_PLAY

export TERM
case "$TERM" in
"network" | "")
    TERM="vt100"
    ;;
* ) pTERM="x"
    until test -z "$pTERM" && tput reset; do
	echo '\nTerminal type is now set to' $TERM
	echo ' <Enter> to confirm, or change if needed:  \c'
	read pTERM
	test -z "$pTERM" || TERM="$pTERM"
    done 
    ;;
esac

exec /usr/local/bin/gopher -s gopher.uoregon.edu


-- 
JQ Johnson
Director of Network Services		Office: 250E Computing Center
Computing Center			Internet: jqj@ns.uoregon.edu
University of Oregon			voice:	(503) 346-1746
Eugene, OR  97403-1212			fax: (503) 346-4397
Newsgroups: comp.infosystems.gopher
From: dorl@vms.macc.wisc.edu (Michael (NMI) Dorl)
Subject: VMS Gopher Client fr Wollongong TCP/IP
Organization:  University of Wisconsin Academic Computing Center
Date: 14 AUG 92 11:49:13    

The other day, I asked if anyone had a working client for
Wollongong WIN/TCP.  It turns out that this has already been 
provided.  Simply compile setting WOLLONGONG=1 on the CC calls
found in COMPILE.COM.

A note to the folks in the home burrow in Minnesota.  How about
putting a few lines in the readme file pointing out the existance
of the WOLLONGONG compile option?  It may save the next fool like
me some time.

Michael Dorl              (608) 262-0466  fax (608) 262-4679
dorl@vms.macc.wisc.edu    MACC / University of Wisconsin - Madison
dorl@wiscmacc.bitnet      1210 W. Dayton St. / Madison, WI 53706
From: raman@cs.cornell.edu (T. V. Raman)
Newsgroups: comp.infosystems.gopher
Subject: Viewing files returned by gopher searches
Summary: gopher display
Keywords: Highlighting getting rid of escape sequences
Date: 15 Aug 92 20:02:04 GMT
Organization: Cornell Univ. CS Dept, Ithaca NY 14853


Hi!

I am using a vt100 terminal with pager set to less.

When I perform searches using gopher, the returned files have the hit
words sorrounded by highlighting characters which are being literally
displayed by my terminal.  Is there some way of getting rid of these
control sequences?

Thanks,

--Raman
-- 
   T. V. Raman <raman@cs.cornell.edu>Tel: (607)255-7421 R 272-2435
		       Office: 5162 Upson Hall,
Department of Computer Science, Cornell University Ithaca NY 14853-6201
		Res: 226 Bryant Avenue Ithaca NY 14850
Newsgroups: comp.infosystems.gopher
From: cowboy@trans.csuohio.edu (Syscrusher)
Subject: Re: will the NeXT users out there please speak ASCII like the rest of us?
Organization: Cleveland State University
X-Newsreader: Tin 1.1 PL4
Distribution: comp
Date: Sat, 15 Aug 1992 14:33:42 GMT

daniel@bauhaus (Daniel Torrey) writes:
: R. P. C. Rodgers, M.D. :
: . 
: . Dear Fellow Gopher List Members,
: . 
: . It seems a signal discourtesy to me to send out messages such as
: 
:  [etc.]
: 
: Don't be silly.  NeXTMail is sort of neat if you have a NeXT; no reason that
: NeXT users should be harassed for using it.  It might be nice if they'd put
: *** NeXTMAIL *** in the subject line, but even if they don't, one can always
: just DELETE IT. 

Also, and you are correct, Bill, the original sender should consider the
basic possibility that the NeXT user simply forgot to switch a setting
on NewsGrazer, most likely, and simply accidentally sent out a rich
post.  I think the original sender should just LET IT GO as a mistake
and move on.


--

________

Joe Rosenfeld                              cowboy@trans.csuohio.edu
Automation Librarian                      joer@inca.law.csuohio.edu
Cleveland State University Law Library
From: TALVELA@ava.hut.fi ("Juhani Talvela" )
Newsgroups: comp.infosystems.gopher
Subject: Bye
Date: 14 Aug 92 18:33:22 GMT
Distribution: comp
Original-To: gopher-news@boombox.micro.umn.edu
X-Mailer: Pegasus Mail v2.3 (R2).

unsubscribe
-- Juhani
=============================================================================
Juhani Talvela                         |    tel: int+358+0+451 2377
Helsinki University of Technology      |         int+358+49+411 806
Laboratory of Space Technology         |    fax: int+358+0+ 460 224
Otakaari 5 A                           | E-mail: TALVELA@AVA.HUT.FI
02150 Espoo, Finland                   |
From: reuver@mikro.ee.tu-berlin.de (Dirk Reuver)
Newsgroups: comp.infosystems.gopher
Subject: gopherd messages on SUN console
Date: 17 Aug 92 13:35:39 GMT
Organization: ZRZ/TU-Berlin

Hi,

I installed gopherd version 1.02 on a Sparcstation. 
The server was compiled with WAIS support, otherwise the
configuration is straightforward. It gets
started from inetd using the following entry in /etc/inetd.conf

gopher  stream  tcp     nowait  root    /usr/new/etc/gopherd    gopherd -I -c -l /usr/new/etc/gopherd.log

the corresponding entry on /etc/services is

gopher		70/tcp				# Gopher info service

whenever a client contacts the gopherd, the following message
is printed on the console

 len(-130371924) greater than max len(2147483647)

The strange thing is that I can't find any part of this message
in the source files of gopherd. So where does this message come
from ? Has anyone else experienced the same ?

Dirk

__________________________________________________________________________
Dirk Reuver    DD6RE                  Phone:  +49 30 314 26705
Institute for Microelectronics        FAX:    +49 30 314 24597
Technical University Berlin           Email:  reuver@mikro.ee.tu-berlin.de
                    "You say tomato, I say tomato"
Newsgroups: comp.infosystems.gopher
From: datta@cs.uwp.edu (David Datta)
Subject: Re: Gopher (comp.infosystems.gopher) Frequently Asked Questions (FAQ)
Organization: University of Wisconsin - Parkside
X-Newsreader: Tin 1.1 PL5
Date: Tue, 18 Aug 1992 16:19:48 GMT

: Q3:  Where are there publicly available logins for gopher.

: A3:  Here is a short list, use the site closest to you to minimize
:      network lag.

:      Hostname                  IP#              Login   Area
:      ------------------------- ---------------  ------  -------------
:      gopher.uwp.edu	       131.210.1.4      gopher  North America

gopher.uwp.edu has been disabled for off-campus use. Sorry.
-- 
-Dave datta@cs.uwp.edu: Man made machines make music for the man.  Now
machines make music while the man makes plans. A second generation, a
generation lost. While the man prepares for the holocaust.- A Flock of Seagulls
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Newsgroups: comp.infosystems.gopher
Subject: Re: Book mark problem with gopher 1.01
Date: 21 Aug 92 03:30:49 GMT
Organization: University of Minnesota, Minneapolis

In <1992Aug18.162617.12421@julian.uwo.ca> reggers@julian.uwo.ca (Reg Quinton) writes:

>Gopher 1.01 seems to have problems with book marks. When you delete a book
>mark nothing much seems to happen, you then hit a <cr> and she core dumps.

>This is repeatable on Sun4 and Mips platforms.

>Does 1.02 fix this problem?

Yes, the problem occurs when you delete the last bookmark.  Another
boundary condition!  1.02 fixes it.

--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | GopherMaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
Return-Path: <jwrzos@cit.hmc.psu.edu>
Date: Wed, 12 Aug 92 08:49:06 EDT
Original-To: gopher-news@boombox.micro.umn.edu
From: jwrzos@cit.hmc.psu.edu
Subject: unsubscribe
Newsgroups: comp.infosystems.gopher
Distribution: comp

SIGNOFF GOPHER-N
Jurek Wrzos
From: TW@UMAB.BITNET
Newsgroups: comp.infosystems.gopher
Subject: Sorry about this...
Date: 14 Aug 92 02:58:15 GMT
Distribution: comp

I hate to post this to the whole list, but I haven't had any luck
in unsubscribing:
 
  Please unsubscribe tw@umab.bitnet (tw@umab.umd.edu)
From: jonabbey@cs.utexas.edu (Jonathan David Abbey)
Newsgroups: comp.infosystems.gopher
Subject: Logging problems with gopherd 1.01
Date: 14 Aug 1992 14:38:18 -0500
Organization: CS Dept, University of Texas at Austin
NNTP-Posting-Host: saltillo.cs.utexas.edu
Summary: gopherd 1.01 no longer does logging for me

Hi folks.  I've recently installed UnixGopher1.1 on a 4.1.2 Sparc Sun system.
The problem I'm having is that the system refuses to log connections at all.

I'm running gopherd as root from inet, chrooting to the appropriate user
directory with -u, and have specified the log file with -l.

e.g., :
gopher          stream  tcp     nowait  root /usr/local/bin/gopherd gopherd \
-unetserv -I -l/usr/netserv/log/gopher.log

I've added spaces after -u and -l, but this changed nothing.  I have it this
way to prevent any problems with the 5 parameter limit in inet.

Any suggestions?  Other like experiences?

-- 
Jonathan Abbey                                 jonabbey@cs.utexas.edu
the university of texas at austin             "He's cleaning up his systems
computer science/math/psychology               to keep his nature pure" - Rush
From: cjc@casbah.acns.nwu.edu (Christopher Chen)
Subject: Gopher 1.02 problem?
Organization: Northwestern University
Date: Tue, 18 Aug 1992 20:05:21 GMT

Has anyone noticed a problem with the BUMMER_STR not getting returned
with the new 1.02 server?  Or is it just me?


cjc
--
Christopher J. Chen  cjc@nwu.edu  (708) 491-4109  (708) 491-3824 fax
Academic Computing and Network Services, Northwestern University
"What was the name of that song?"			-- Nick Kotzamanis
"It was two measures!  You don't *name* two measures!"	-- Jim Gellman
From: jml4@cus.cam.ac.uk (John Line)
Newsgroups: comp.infosystems.gopher
Subject: Re: Scripting and passwords
Date: 22 Aug 92 13:02:16 GMT
Organization: U of Cambridge, England

In article <1992Aug19.165301.17332@news.uiowa.edu> jones@pyrite.cs.uiowa.edu (Douglas W. Jones,201H MLH,3193350740,3193382879) writes:
>From article <1992Aug19.162108.9984@news.weeg.uiowa.edu>,
>by isca@umaxa.weeg.uiowa.edu (Iowa Student Computer Association):
>>
>> read( f -- s )
>> 	Reads a string from the file, connection, or user.  NOTE!  If the user
>> 	types in his or her password, the program is terminated and the result
>> 	is NOT returned.
>
>You mean to say that, if by coincidence, the string I type in response to a
>prompt happens to be the same as the string I use as a password, things will
>bomb?  This won't be very pleasant for users who happen to have poorly chosen
>passwords.  For years, for example, my password was "tree" (yep, 4 letters,
>lower case only, all among the 10 most common letters in English text).

I, too, don't like the idea of perfectly reasonable (at least in some contexts)
response being rejected just because it happened to match my password. But more
important - isn't the rejection in itself likely to be a big security risk?

For example, what happens if someone is looking over my shoulder (maybe I'm
demonstrating how to use gopher) and it rejects my input, which anyone could
see, because it matched my password... Better yet, it's up on big display
monitors for a whole classroom of students to see... It can't just ignore
the input quietly (substitute null string, or whatever), or I (at least, J.
Random User...) could spend all day trying to get the "stupid thing" to work.

That seems like as serious a risk (especially if I wasn't aware that someone
walking past in a public terminal room had looked over my shoulder at the
critical moment - probably too busy cursing the *@!# software) as being fooled
by a trojan-horse password prompt...

                                John
-- 
John Line - Cambridge University Computing Service, Computer Laboratory,
            New Museums Site, Pembroke Street, Cambridge CB2 3QG, ENGLAND.
Internet: jml4@cus.cam.ac.uk  JANET: jml4@uk.ac.cam.cus  Phone: +44 223 334708
Date: Fri, 14 Aug 92 16:32:25 EST
From: cooper@utopia.cc.nd.edu
Original-To: gopher-news@boombox.micro.umn.edu
Subject: RE:  Zen and the art of Gopher
Newsgroups: comp.infosystems.gopher
Distribution: comp

There is a localized version of a general "What is Gopher" document  
sitting at the Notre Dame Gopher in "About the Notre Dame  
Gopher"/Gopher class document.  It is admittedly slightly dated but  
you are welcome to check it out and comment (to me, not to the list)  
if you wish.

Looking at the Gopher FAQ may also be of interest

Joel
---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joel P. Cooper                         Phone: 219-239-7221
Asst. Director, Networking Services    Fax:   219-239-8201
Office of University Computing         Email: cooper@utopia.cc.nd.edu
University of Notre Dame
Notre Dame, IN  46556

                    "Information is our friend."
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Newsgroups: comp.infosystems.gopher