HDTenEightyP/NetNews huggingface dataset:
From: gilbertd@sunflower.bio.indiana.edu (Don Gilbert)
Subject: Re: The Macintosh GopherApp
Organization: Biology, Indiana University - Bloomington
Date: Fri, 21 Aug 1992 22:51:24 GMT

bk@Turing.ORG (Brian Knatz) writes:
> I want to make a
> GopherApp file that opens automatically to our own hole.  
>
> "New Gopher Link" or "Edit Gopher Link" options under the "Internet"
> menu, but both options are grayed out

The response from Eiji Hirai (thanks) is probably your best answer, but 
let me give a few more.

I get a lot of questions about this.  That is an indicator I need to
rewrite it again.  I think my choice, to inactivate these items for 
the default/general case is correct.  You don't want your
average gopher user trying to edit gopher links (they need to know
what goes into a gopher link, and messy things about mac systems if
they are to get it right).  However, for those who know a bit, this
editing of gopher links is easier than the Text/Resedit method.  Maybe
the next release will hide these menu items entirely until the user
reads the fine print.

Also, I confess, the help file may not explain how to activate 
those items (writing help tends to be last and least with me).
The trick is to select the Gopher Prefs menu item, and scroll down the
prefs dialog until you find "Allow new & edit links", and check that box.

Those who want to tell GopherApp to use a new default set of links (like
to your own server), you can do it without using Resedit.  Scroll a bit
farther down the Prefs dialog 'til you find "Default new window" and
hit the "Save front window" button.  This will make whatever the current
front Gopher window is to be your new default choice (what appears if
you launch GopherApp alone rather than from a Gopher folder document).
This change is made in the "GopherApp Preferences" file, not in the
GopherApp application file, so if you want to distribute this change to
others, you need to also distribute the Preferences file (from
System Folder:).

-- 
Don Gilbert                                     gilbert@bio.indiana.edu
biocomputing office, biology dept., indiana univ., bloomington, in 47405
Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: Problem searching with PC Gopher
Organization: University of Minnesota, Minneapolis
Date: Fri, 21 Aug 1992 04:40:53 GMT

In <7149@lib.tmc.edu> snewton@oac.hsc.uth.tmc.edu (Steven E. Newton) writes:

>>Well, the problem is (and the author knows this), PC Gopher II is written in 
>>Pascal, which has a limit of 255 chars per STRING type.  Unfortunetly, 
>>searches can result in longer than 255 chars returned.  This means the PC 
>>Gopher client doesn't work correctly.  Note that the author is well aware of 
>>the limitation and is planning on (correct me if I am wrong) re-writting the 
>>client in C/C++.
>>

>If you would be able to use it, there is a DOS port of the Unix gopher
>client that we worked on here.  It is for FTP Software's PC/TCP and is
>based on the 0.9 client but has most of the functionality of the 1.0
>client, except the .gopherrc and bookmarks.  It's been tested with
>PC/TCP 2.04 and 2.05, but it might work on other versions.

>It does support the GIF and sound file types.  Also, it is hardcoded to
>connect to our server, cwis.uth.tmc.edu, but you can give it the
>appropriate command-line arguments.  Available in a self-extracting
>zip archive for anonymous ftp from oac.hsc.uth.tmc.edu as
>/public/dos/misc/dosgofer.exe.

For those of you wanting to access this, I've added the information to
the FAQ and also added a .Link to boombox's gopher server so you can
just browse under Gopher Software Distribution.

Funky man!
--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | GopherMaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
Newsgroups: comp.infosystems.gopher
From: jqj@duff.uoregon.edu (JQ Johnson)
Subject: Re: cookbook for secure gopher wanted
Organization: University of Oregon Network Services
Date: Fri, 14 Aug 92 23:16:18 GMT

Thanks to the many people who responded with advice on setting up a
secure telnet->gopher gateway.  Per the advice of a number of people, I
used the minimalist "more" program found in Gopher_tools.tar, and a
hacked version of telnet that disallows shell escapes and off-campus
destinations, along of course with a shell wrapper that sets the
appropriate environment and calls the standard gopher with "-s").  I
also (important) turned off support for metamail (MIME) and sound files.

I'm still not convinced that my gateway is secure, though.  The Unix
gopher client is a moderately complex program, and was not originally
written with security in mind.  Has anyone gone over it carefully
looking for holes?  For example, it appears to me that it is
susceptible to the Morris attack of overwriting function return
addresses by providing too much input to CURGetOneOption().  What
other such holes (especially ones easier to exploit) exist?

-- 
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
From: JFORD@ua1vm.ua.edu (James Ford)
Newsgroups: comp.infosystems.gopher
Subject: Re: anonymous ftp
Date: 14 Aug 92 17:58:11 GMT
Organization: The University of Alabama, Tuscaloosa

In article <1992Aug13.142510.14183@newton.ccs.tuns.ca>
greene@newton.ccs.tuns.ca (Courtney Greene) writes:
>
>I'm trying to configure gopher to open an anonymous ftp session to
>splicer.cba.hawaii.edu. When I use ftp, non-gopher, I am placed in
>the following directory
>
>                g:\files
>
>My question is, how can I specify this in my link file?
 
There is a problem.  When you anonftp to a Unix machine, you can issue
the command "ls -F" to get a directory listing.  I believe this is what
g2fd.c and ftp.c (in gopherd) uses.
 
However, Splicer (and VM/CMS machines for that matter) do not understand
the "-F" option for "ls".  So, you get screwed up information and Gopher
can't parse it correctly.
----------
James Ford -  Consultant II, Seebeck Computer Center
              The University of Alabama (in Tuscaloosa, Alabama)
              jford@ua1vm.ua.edu, jford@seebeck.ua.edu
              Work (205)348-3968  fax (205)348-3993
From: AMOODY@MAINE.MAINE.EDU
Newsgroups: comp.infosystems.gopher
Subject: Re: Gopher Server NLM for Novell NW386, anyone want one?
Date: 12 Aug 92 17:01:22 GMT
Distribution: comp
Organization: University of Maine System

Brad,
I think an NLM gopher server would be a wonderful idea!  I too am concerned
that the user need only deal with an environment that they are familiar
with.  My only problem is that many of the servers on campus are Netware
2.x and an NLM would not do them any good.  Maybe a stand alone DOS based
gopher server that could handle several Novell servers would be the best
solution in that case.  Gee... can I vote for both? ;-)

Andrew C. Moody
Unix Systems Analyst
AMOODY@MAINE.MAINE.EDU
From: cooper@utopia.cc.nd.edu
Newsgroups: comp.infosystems.gopher
Subject: RE: Using mail to provide gopher data
Date: 14 Aug 92 21:57:34 GMT
Distribution: comp
Original-To: gopher-news@boombox.micro.umn.edu

Joy.Lynam sez:

> This method as been a good way for us to use a common application  
(mail) to
> distribute the job of loading gopher data.  And, users can own and
> maintain their data.  We've just begun doing this so we it's not  
refined.
> But we think we it's a great idea.

We do too.  We have implemented posting via email at ND and think  
it's sort of a nice way to do things.  We have:

1. AFS (Andrew File System) filespace for everyone on campus,
2. a central email service which uses the
3. CSO Nameserver

AFS gives us a common filespace to save user data in.  The central  
email service gives us a common place to deal with email addresses.   
The CSO nameserver is loaded with "official" information about folks  
who want to be Information Providers.  With this stuff in place, it  
is a manageable task to grab stuff out of Information Providers'  
~/gopher directories, check it, add some "neat header information" to  
it such as department, email address, and like that.

Information Providers can either copy their files to ~/gopher (if  
they are native AFS users), use an FTP utility to get them there, or  
send mail messages to a posting address where mail gets accepted ONLY  
if the Info Provider is "authorized".  All others get a "gentle"  
thumb-to-noser.

We have a document template we ask folks to use which includes an  
expiration date (when do you want this to go away?), a title (what do  
you want this to be called in Gopher_space), keywords (for  
searching), and an optional Path field (for email users who want to  
create a subdirectory in their part of Gopher_space).

When a document is checked for posting to Gopher_space, the Info  
Provider gets an email message back.  If there was something wrong  
(did the Info Provider copy an MS Word document instead of text?) the  
mail message advises that there was a problem.  If the document is  
posted successfully, the happy "your document name_goes_here was  
successfully posted to gopher_space" message is sent off to the Info  
Provider.

The feedback loop is cool 'cause it's at least some means of  
notifying an Info Provider that someone just impersonated them.

Ultimately we would like to see the email thing go away.  That will  
happen when PC's and Macs get to play in AFS filespace.

Joel
Newsgroups: comp.infosystems.gopher
From: reuver@mikro.ee.tu-berlin.de (Dirk Reuver)
Subject: maildir retrieved - bug ?
Organization: ZRZ/TU-Berlin
Date: Mon, 17 Aug 1992 15:07:30 GMT

Hi,

found a strange line in the gopher log file the other day:

Sun Aug 16 12:48:04 1992 22265 0.0.0.10 : retrieved maildir ozart

the strange thing is there doesn't exist a file 'ozart' within
our gopher data. The gopherd should have loged an error, I suppose.

The other strange thing is the IP-address - never seen any such address
Are these addresses used for test purposes ?

Any help appreciated

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"
From: mtm@SUMEX-AIM.Stanford.EDU (Mike Macgirvin)
Newsgroups: comp.infosystems.gopher
Subject: RE: binary types
Date: 19 Aug 92 18:53:51 GMT
Reply-To: mtm@SUMEX-AIM.Stanford.EDU
Distribution: comp
Original-To: Earthworm society <mahilata@vogon.mathi.uni-heidelberg.de>
Original-Cc: gopher-news@boombox.micro.umn.edu
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


>On the other hand, why count a .ps as binary? Here I can perfectly look at a
>.ps in my "less" (yes, its a "less -r") window, and decide to print it
>by the p buttom. (Printing does not work out of NeXT Gopher, though)

	Because different PostScript creation mechanisms do different things 
with "end-of-line". It is not necessary to even have line breaks in PostScript, 
and I have seen many examples which didn't. Different machines will generate 
different sequences when they -do- use end-of-line, such as CR only, LF only, 
CRLF, etc., and the system reading the line might not use the same format. Even 
though it is ASCII text, many programs will choke if they get an input line 
larger than their default buffer size (which varies). There are also instances 
of PostScript which use "CTRL-D" to end dictionary definitions, (while there is 
still more text in the file). Under Unix, it is an "end-of-file", and again, 
some programs will not like this.

"mike" (Mike Macgirvin)         Mike_Macgirvin@CAMIS.Stanford.EDU
Unix Server Administrator       CAMIS Computer Project
Newsgroups: comp.infosystems.gopher
From: jmay@ctp.com (Jason May)
Subject: gopher client for Windows?
Date: Fri, 14 Aug 1992 19:57:56 GMT
Organization: Cambridge Technology Partners


Has anyone written a gopher client for Windows 3.x?  pcgopher
is nice, but I couldn't get it to work from a PIF file.

Thanks,
-Jason (jmay@ctp.com)
From: jsantos@tolten.puc.cl (Juan Manuel Santos)
Newsgroups: comp.infosystems.gopher
Subject: unsubscribe
Date: 13 Aug 92 23:44:26 GMT
Distribution: comp

Please unsubscribe me, I prefer news

Juan Manuel Santos
Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: Gopher 1.02 problems
Organization: University of Minnesota, Minneapolis
Date: Fri, 21 Aug 1992 03:57:04 GMT

In <mtm.714171322@CAMIS> mtm@camis.Stanford.EDU (Mike Macgirvin) writes:

>peterson@choctaw.csc.ti.com (Bob Peterson) writes:

>>  Under Gopher 1.01 I implemented access to a local Archie server.  To
>>implement Archie access I modified Mike Macgirvin's shell script
>>examples (see his article <mtm.711060422@CAMIS>, posted on 13 Jul 92).
>>The scripts provide access to the command line Archie client.  However,
>>under Gopher 1.02 the scripts fail, apparently forcing the server into
>>an infinite loop.  Unless someone else knows the solution, I'll
>>continue working this problem.

>	I originally fixed this and sent the patches back to UMN, but
>it looks like it affects something else, so the fix was undone in the
>1.02 release. Look in "object/GDgopherdir.c" at about line 268 for a line
>that is commented out containing "return(j);" and remove the comments.
>Perhaps somebody can tell me/us why it needs to be commented, but it
>cause the endless loop you describe. I have seen no ill effects with
>the line uncommented.

Well, I don't think it's supposed to be uncommented.  I'll do some
extensive testing and see why it's that way or the other.

As far as the number of arguments to ropen(), it's emulating the
open() call:

     int open(path, flags[ , mode ] )
     char *path;
     int flags;
     int mode;

The mode is optional.  For the read open() calls it doesn't matter.
--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | GopherMaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
Date: Wed, 12 Aug 1992 20:50:40 -0800
Original-To: gopher-news@boombox.micro.umn.edu
From: dmanning@nero.UVic.CA
Subject: Gif/linking test directory
Newsgroups: comp.infosystems.gopher
Distribution: comp

For folks who want to test out a new copy of our GIF/document linking aware
XGopher client there is a 
test directory on our gopher server "kafka.uvic.ca" called (oddly enough)
"Test Gif Clients Here". In it you can find a few images and a few example
text files with links to them. The directory is indexed to give you an idea
how this kind of thing might be used.


                                                                           
            Dave Manning
From: lizard+@CMU.EDU (Robert Joseph Kuszewski)
Newsgroups: comp.infosystems.gopher
Subject: Re: Forwarding links
Date: 20 Aug 92 13:32:38 GMT
Organization: Distributed Workstation Services, Carnegie Mellon, Pittsburgh, PA


The method we have chosen to deal with the problem of servers moveing
from machine to machine is this:

For each gopher server we have running, we aliased the machine to
something like:

	gopher-servX@andrew.cmu.edu

and tell everyone to connect to that machine.

When we move the server to another machine, we simply move the alias
with it.  The end user will have no idea that the server changed and we
don't have to worry about outdated links from now till doomsday.

-Bob
Newsgroups: comp.infosystems.gopher
From: dbeedle@rs6000.cmp.ilstu.edu (Dave Beedle)
Subject: g2nntp Access syntax?
Date: Wed, 12 Aug 1992 19:10:06 GMT
Organization: Illinois State University

   I'm using g2nntp to allow reading of the net news.  I need to restrict 
access to a particular set of groups to those machine on campus.  What is the 
syntax to specify in the g2nntp script?  I can find no notes on it and the 
example looks cryptic!  Also, where can updates of g2nntp be found?  Thanks!
-- 
  Dave Beedle                                    Office of Academic Computing
                                                    Illinois State University
  Internet:  dbeedle@rs6000.cmp.ilstu.edu                    136A Julian Hall  
  "Relax, don't worry!  Have a homebrew!"                  Normal, IL   61761
Newsgroups: comp.infosystems.gopher
From: mtm@camis.Stanford.EDU (Mike Macgirvin)
Subject: Gopher+ Client desired feature
Organization: DSO, Stanford University
Date: 21 Aug 92 16:51:30 GMT

	
	Something I'd like to see in an advanced Gopher+ client (maybe
because of overhead this wouldn't be efficient on some systems), is
for the client to keep a date pointer to the current gopher dir when
you access a document within it. Then you could have a basis for
highlighting "new items" when you access that dir at a future date.
The restriction on keeping the date only if you accessed a document
there would help keep this list to a "reasonable" size, since we often
browse a lot, but there are a finite number of things which interest
us.
	You know, a system like that could form a basis for a next
generation USENET. This one's getting real choked... Think about it...

mike
From: jqj@duff.uoregon.edu (JQ Johnson)
Newsgroups: comp.infosystems.gopher
Subject: cookbook for secure gopher wanted
Date: 13 Aug 92 17:19:23 GMT
Organization: University of Oregon Network Services

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. 
I note that other sites do this, and was wondering if anyone had a
cookbook for setting it up securely.  My initial attempt at doing so
(using the -s flag and setting environment vars) resulted in a rather
insecure scheme.  Must I go to the effort of running the gopher client
chroot() and producing a hacked version of telnet?

My concerns:
   - "builtin" internal pager doesn't seem to work in gopher 1.02, and
     PAGER=more allows escaping to vi and thence to arbitrary commands
   - ability to run metamail to display MIME files opens lots of 
     potential security holes
   - by default, "gopher -s" allows mailing of downloaded files
   - 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
   - etc.  I haven't done enough analysis to be at all confident that
     my set of concerns is exhaustive

-- 
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: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
Subject: Re: Forwarding links
Organization: University of North Texas
Date: Thu, 20 Aug 1992 18:15:31 GMT

lizard+@CMU.EDU (Robert Joseph Kuszewski) writes:

>When we move the server to another machine, we simply move the alias
>with it.  The end user will have no idea that the server changed and we
>don't have to worry about outdated links from now till doomsday.
>
That is what I am trying to move to.  The largest problem is that "+"
returns the official hostname.  Someone from Chicago (sorry, forgot your
name) showed me a one-line patch to work around that.

Newsgroups: comp.infosystems.gopher
From: mtm@camis.Stanford.EDU (Mike Macgirvin)
Subject: Re: waisindex-ing a gopher directory but avoiding .cap and .cache
Organization: Stanford School of Medicine
Date: Wed, 12 Aug 1992 17:33:58 GMT

In article <mtm.713637787@CAMIS> mtm@camis.Stanford.EDU (Mike Macgirvin) writes:
+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...

+	Well, you could always
+
+	find $gopherdir -name '[^.]*' -exec waisindex -a $otheropts {} ';'

I will TEST before I post...
I WILL test before I post...

	Forgot that "find" has it's own wierd regex's, and implements
negation a bit differently than ls... The above should be

	find $gopherdir \! -name '.*' -exec waisindex -a $otheropts {} ';'

mike
From: ccoprmm@prism.gatech.EDU (Michael Mealling)
Newsgroups: comp.infosystems.gopher
Subject: Re: Resource Discovery Service for gopher
Date: 13 Aug 92 07:05:47 GMT
Organization: Georgia Institute of Technology

In article <65729@hydra.gatech.EDU> ccoprmm@prism.gatech.EDU (Michael Mealling) writes:
>To avoid the confusion we should do both _seperately_. That is:
>1) Setup an administrative type that the clients don't display but that
>   has a standardized descriptive name since not all servers will have
>   the same path conventions.
>
>For #1 I think we should have Type=A for Administrative and the name for
>the index of resources to be "Local Resources". Have the clients still
>recieve these entries but not display them. Obviously they can still be
>viewed if the user really wants to but that is left up to the client.

 This one was easier than I thought (at least for the Unix curses client).
All you need to do is change GDgopherdir.c so that the function
GDfromNet() has this big if statement before it adds TempGopher to gd. You
also need to add the A_EXCLUDED and A_EXCLUDEF entries to the list of
types in the objects directory. Now how the client deals with these if
this line is left out is to put A_EXCLUDED and A_EXCLUDEF in the big case
statement in gopher.c so that they execute the same as A_DIRECTORY and
A_FILE. I specified an "X" for the type character when I was playing around but
I think "A" and "a" would be better. Any problems with this? 


	  if ((i==0) && (GSgetType(TempGopher) != A_EXCLUDED) && (GSgetType(TempGopher) != A_EXCLUDEF)) {
	       GDaddGS(gd, TempGopher);
	       if (eachitem != NULL) 
		    eachitem();
	  }

-- 
------------------------------------------------------------------------------
Michael Mealling                     ! Hypermedia WWW, WAIS, and gopher will be
Georgia Institute of Technology      ! here soon via MIME. Your view of the 
Internet: michael@fantasy.gatech.edu ! internet is about to change completely!