HDTenEightyP/NetNews huggingface dataset:
From: dinn@ug.cs.dal.ca (Michael 'Moose' Dinn)
Subject: Gopher "whatisit" file and a new Gopher
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Date: Wed, 19 Aug 1992 16:45:39 GMT


Is there a "What is Gopher, what are it's features?" file out there?
I've been given the task of doing an article on Gopher for a local newsletter, 
and I figure that this would be easier to give in than writing one (if it
exists :)

Also, there's a Gopher server at ug.cs.dal.ca port 3442 (Dalhousie's Gopher
Service).

--
 Michael Dinn, Sysop of the Moose's Swamp - Nova Scotia's largest Amiga BBS
 +1 (902) 492-1035 * HST/V.32 & V.42bis * 300-14,400 baud * 220 Megs online
 dinn@ug.cs.dal.ca * moose@swamp.UUCP       | The best way to accelerate a
 Moderator of comp.[sources|binaries].amiga | Mac is at 9.8 m/s/s.
From: davet@granta.uchicago.edu (David Thomas)
Newsgroups: comp.infosystems.gopher
Subject: Personalizing gopherspace
Date: 14 Aug 92 18:05:26 GMT
Organization: University of Chicago, Astronomy and Astrophysics


Has anybody thought about changing the gopher clients (I'm thinking
particularly about the curses and X clients, but it should presumably
apply to the others) to do the following: Arrange that when the client
starts, instead of contacting a server, it looks in say $HOME/gopher,
and if it finds it, presents the data in the usual way.  (If there's
no such directory then it goes on to look for a (default) server.)  A
user could still make contact with the rest of gopherspace by
including link files in ~/gopher, but would also have access to
whatever data he or she keeps locally.

There are two main advantages that I see to this scheme.  First, a
user can use the same tool (gopher) for browsing their own information
as for searching through the internet, without having to run a server
and make (possibly sensitive) personal data at least partially public.
Secondly, by populating your own gopher directory with links you can
both access services that may not appear elsewhere in gopherspace
(like telnet'able information services) and provide quick access to
your own favorite gopher holes -- when I come across a useful
resource, instead of trying to make a mental note of where it is, how
I accessed it (gopher, WAIS, ftp) and what path to take to get there,
I just put a link into my own private map of gopherspace.

It seems like this shouldn't be a difficult problem, although it would
mean copying some of the server code into the clients.  Is anybody
else out there thinking along these lines?
-- 
David Thomas                        University of Chicago
davet@oddjob.uchicago.edu           Astronomy and Astrophysics
Newsgroups: comp.infosystems.gopher
From: cameron@chara.cs.sfu.ca (Rob &)
Subject: Re: .gopher files
Reply-To: cameron@chara.cs.sfu.ca
Organization: SFU
Date: Fri, 14 Aug 1992 21:33:36 GMT

Yes!  Replacing .cap directories and .link files with a single .gopher file
would be great! 

Furthermore, it would also be nice if we could omit the Numb= entries and
simply use the order of entries in the .gopher file as the menu order.
It would make menu insertions/deletions so much easier.

Rob Cameron                               cameron@cs.sfu.ca
School of Computing Science
Simon Fraser University
Burnaby, B.C.  V5A 1S6
From: billy@sol.acs.unt.edu (Billy Barron - VAX/UNIX Systems Manager)
Newsgroups: comp.infosystems.gopher
Subject: Links pointing at sol.acs.unt.edu
Date: 18 Aug 92 20:03:23 GMT
Organization: University of North Texas

To any gopher admins pointing at sol.acs.unt.edu (this includes you, Ed! :-),
place change your links to point at gopher.unt.edu instead as the server
may (probably) move in the future.  My server is now patched to think it
is gopher.unt.edu (thanks to the guy who showed me trick).
Newsgroups: comp.infosystems.gopher
From: reggers@julian.uwo.ca (Reg Quinton)
Subject: Book mark problem with gopher 1.01
Organization: University of Western Ontario, London
Date: Tue, 18 Aug 1992 16:26:17 GMT

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?
From: rbppjr@rohmhaas.com
Newsgroups: comp.infosystems.gopher
Subject: bye ...
Date: 14 Aug 92 14:10:49 GMT
Distribution: comp
Original-To: gopher-news@boombox.micro.umn.edu

SIGNOFF GOPHER-N
From: devet@wsinis08.info.win.tue.nl (Arjan de Vet)
Newsgroups: comp.infosystems.gopher
Subject: Bug in gopherd 1.02 securityfile code
Summary: internet address matching does not work
Keywords: gopherd, security, internet addresses
Date: 21 Aug 92 21:29:33 GMT
Reply-To: devet@info.win.tue.nl
Followup-To: comp.infosystems.gopher
Organization: Eindhoven University of Technology, the Netherlands


There's a bug in the function Can_Read in gopherd.c (1.02):

boolean
Can_Read(sockfd)
  int sockfd;
{
[...]
     length = sizeof (sa);
     getpeername(sockfd, &sa, &length);
     inet_netnames(sockfd, &sa, host_name);
[...]
	  if (isdigit(*cp)) {
	       /** Internet address x.x.x.x ..***/
	       /** Check for a match from the beginning **/
	       if (strstr(host_name,cp) == host_name)
		    return(MatchReturn);
		    
	  }
	  
	  else if (*cp == '*') {
	       return(MatchReturn);
	  }

	  else if (*cp != '#') {
	       /*** Not a comment, must be a host name **/
	       if ((strstr(host_name, cp) + strlen(cp)) == (host_name + strlen(host_name))) {
		    return(MatchReturn);
	       }
	  }
[...]

The variable host_name contains the *name* and not the internet address, so
comparing host_name with an Internet address as is done above is not very
usefull. Does anybody know how to get the internet address of the host
connected to sockfd? If you have a patch, please post.

On SUN OS 4.1.1 host_name does not contain a fully qualified domain name
(e.g., it gives `foo' instead of `foo.bar.edu') if the connection comes from
within the same domain. That's the reason why I tried the numerical variants
in the securityfile, but they didn't work because of the bug described above
(if anybody has a patch for this problem, it'll be appreciated too).

Arjan
Newsgroups: comp.infosystems.gopher
From: lindner@mudhoney.micro.umn.edu (Paul Lindner)
Subject: Re: .gopher files
Organization: University of Minnesota, Minneapolis
Distribution: comp
Date: Tue, 18 Aug 1992 05:53:01 GMT

In <dominic.5.714023376@csc.mgate1.cuhk.hk> dominic@csc.mgate1.cuhk.hk (Dominic Chow) writes:

>In article <MAILQUEUE-99.920814102151.75@rc.rug.nl> HAIJKO@RC.RUG.NL writes:
>>
>>He showed me a patch he made on the gopherd software.
>>The most important improvement he made was the introduction of a
>>.gopher file to replace .cap and .link
>>

>We do have a similar implementation.  We do hope this feature to be included 
>in the standard distribution.

Yes, yes.  I like it too and will be working shortly to add it into
the first gohper+ server release.  Stay tuned.



--
 | Paul Lindner | lindner@boombox.micro.umn.edu   | Slipping into madness
 |              | Computer & Information Services | is good for the sake
 | GopherMaster | University of Minnesota         | of comparision.
///// / / /    /////// / / / /  /  /  /   /      //// / / / /  /  /  /   /
Xref: sparky comp.infosystems.gopher:234 alt.hypertext:693 comp.infosystems.wais:402
From: smj@beta.lanl.gov (Stephen M. Johnson)
Subject: Gopher and CD-ROM on MAC
Organization: Savannah River Site
Date: Tue, 18 Aug 1992 21:05:08 GMT

I am trying to set up the UMN Macintosh server and would like to be able
to support aliases and/or CD-ROM. Is this possible? Can I support CD from
other servers i.e. UNIX?
-- 

Mark Johnson			| Westinghouse Savannah River Company
				| (803) 644 1494
smj@lanl.gov			| Aiken, South Carolina
From: mike@rs1.tcs.tulane.edu (michael pilman)
Newsgroups: comp.infosystems.gopher
Subject: Help compiling Gopher server on AT&T UNIX sysV386
Date: 22 Aug 92 18:00:26 GMT
Organization: Tulane University, New Orleans, LA
Nntp-Posting-Host-[nntpd-229]: rs1.tcs.tulane.edu


I am interested in hearing from anyone who has compiled a 
gopher server on a machine with the following configuration
or one similar.

386 AT&T UNIX sysV386 r3.2.3 w/ ANSI C SysV from AT&T.

Any input would be appreciated.  Please E-mail to me as I 
am cross posting and may not get back to this group soon.

Mike Pilman                       |  mike@rs1.tcs.tulane.edu
Facilities Administrator          |
Computing Services                |
Tulane University                 |
Newsgroups: comp.infosystems.gopher
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: Gopher for MS-Windows?
Organization: Draper Laboratory
Date: Wed, 12 Aug 1992 17:50:00 GMT

Does anyone know if there is a Gopher client for OS/2 and/or
MicroSoft Windows?

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
From: zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby)
Newsgroups: comp.infosystems.gopher
Subject: Re: waisindex-ing a gopher directory but avoiding .cap and .cache
Date: 12 Aug 92 10:34:46 GMT
Reply-To: M.Whidby@mcc.ac.uk
Organization: Manchester Computing Centre

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?

The only way I know to avoid this is not to use the recursive option and
do each subdirectory manually. Bit of a pain really.
-- 
How about my gopher sig:

Name=Mark Whidby
Numb=1
Host=hpc.mcc.ac.uk
Path=Distributed Systems/Manchester Computing Centre
Newsgroups: comp.infosystems.gopher
From: blackp@med.umich.edu (Jeremy Thomas James)
Subject: Novell LWP Client now available!!!
Originator: blackp@hendrix.itn.med.umich.edu
Organization: University of Michigan - Medical Center
Date: Thu, 20 Aug 1992 19:59:55 GMT


  I have finished a beta release of a Lan Workplace for DOS version of 
the gopher client.  It can be downloaded from lennon.itn.med.umich.edu with
anonymous ftp from the gopher/ subdirectory.  There is a small doc with it
explaining a little bit about it.  Just remember it is beta, so use it
at your own risk.  There are still quite a few bugs to be worked out, but it
is at least usable for now.
Send questions or comments to : blackp@med.umich.edu
-- 
What I say isn't necessarily the opinion of the organization I belong to!
===============================================================================
Jeremy T. James         University of Michigan Medical Center,  ITN 
B1911 CFOB, Ann Arbor, MI 48109-0704 Phone:313-747-2778  blackp@med.umich.edu
"Even if your on the right track, you'll get run over if you're there too long"
-------------------------------------------------------------------------------
From: schemers@Slapshot.Stanford.EDU (Roland Schemers)
Subject: Re: g2nntp Access syntax?
Organization: Distributed Computing Group, Stanford University
Date: Wed, 12 Aug 92 22:12:27 GMT


In article <1992Aug12.191006.13434@rs6000.cmp.ilstu.edu>, dbeedle@rs6000.cmp.ilstu.edu (Dave Beedle) writes:
|>    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!

@nntp_acl=(
#     ipaddress  group    access + = allow, - = deny
     '^36\.      .*       +',
     '.*         ^clari   -',
     '.*         .*       +'
  );


Where ipaddress is a perl regular expression, and group is also a perl
regular expression. The + means allow access, and the - means deny.

This example allows any IP address starting with "36." full access, denies 
access to any group starting with "clari." to everyone else, and gives
full access to the rest of the groups.

The ACLs are parsed in order until a match is found, so you need to list
the most restricted (or permissive) ACLs first.

I guess that would be me :-) The latest version should be in the 
pub/gopher/incoming directory on boombox.micro.umn.edu.  The syntax
for the acl is basically:


-- 
Roland J. Schemers III              |            Networking Systems
Systems Programmer                  |            168 Pine Hall   (415)-723-6740
Distributed Computing Group         |            Stanford, CA 94305-4122
Stanford University                 |            schemers@Slapshot.Stanford.EDU
Newsgroups: comp.infosystems.gopher
From: mtm@camis.Stanford.EDU (Mike Macgirvin)
Subject: Re: waisindex-ing a gopher directory but avoiding .cap and .cache
Organization: DSO, Stanford University
Date: 12 Aug 92 16:43:07 GMT

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

	Well, you could always

	find $gopherdir -name '[^.]*' -exec waisindex -a $otheropts {} ';'

	--- just be sure you don't specify $gopherdir as ".", but I
  think it needs a full path anyway for the indexes to work right.

mike


	
Newsgroups: comp.infosystems.gopher
From: GO.MSB@isumvs.iastate.edu 
Subject: Re: Gopher for the Technically Impaired
Organization: Iowa State University, Ames IA
Distribution: usa
Date: Fri, 14 Aug 1992 15:11:36 GMT

In article <9208141050.AA00896@glnpogis5.r05.epa.gov>,
blm@glnpogis5.r05.epa.gov writes:
>
>Subject: Gopher for the Technically Impaired
>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
>****************************************************************************
>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
>****************************************************************************
"Zen and the Art of the Internet" explains the Internet in general...

Is this something new?  Sounds great.  Is it on-line or on pulverized trees?
Any pointers to it would be greatly appreciated.  Thanks.

Marvin Beck   Iowa State University
Newsgroups: comp.infosystems.gopher
From: jones@pyrite.cs.uiowa.edu (Douglas W. Jones,201H MLH,3193350740,3193382879)
Subject: Scripting and passwords
Date: Wed, 19 Aug 1992 16:53:01 GMT
Organization: University of Iowa, Iowa City, IA, USA

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

Now, I agree that users should chose non-English passwords that are "hard to
guess", but I also feel that making it illegal to type a string that happens
to be my password is a bit fishy.  Here is my primary reason:

   The interpreter shouldn't know my password.  Decent security systems limit
   the use of passwords as much as possible, both outside the system and
   inside.  Ideally, the client code (where the interpreter seems to run)
   shouldn't know the password, it should only know that the user has already
   been authenticated.  Only the authentication gateway should ever see the
   password!

There is a complementary side to this:

   Users must be aware that, every time they are asked for a password, there
   is a possibility that they are being asked by a trojan horse.  Ideally,
   users should know that they are never going to need to present a password
   other than at well-known points in the dialog, such as at the very start,
   when they are asked to log in or as part of the dialog used to change an
   old password.  If the user sees a password request at any other time, the
   user should assume that something is wrong and terminate the session
   immediately.

As a general rule, I consider any system which does not allow me to work this
way to be woefully inadequate and I won't use it except under duress.
When appropriately configured, UNIX works this way, although in the network
environment, it doesn't work as well.

The Unix logout/login sequence can still be faked by a trojan horse, though,
so I prefer the model used by the Illinois Plato system, where the standard
way to get a login prompt was to kill your session with a keystroke
sequence that was guaranteed to terminate any running applications in either
the Plato Programmable Terminal or on the mainframe.

					Doug Jones
					jones@cs.uiowa.edu

kkk
Newsgroups: comp.infosystems.gopher
From: thor@teetot.acusd.edu (Mr. Nelson Thor Brickman)
Subject: Compiling Wais Gopher
Organization: usd
Distribution: usa
Date: Wed, 12 Aug 92 16:10:15 GMT

Hi,

  Quite a few people have had trouble compiling the WAIS/Gopher indexing
stuff.  I finally got mine to work ( on Ultrix 4.2 ) so I thought I
would put the fixes I used up on our gopher ( University of San Diego,
teetot.acusd.edu, Port 70 .)

  I hope this helps if people have trouble.

Thor
( Gopher Trainer )
-- 
It's all small shit.
tb
From: mtm@camis.Stanford.EDU (Mike Macgirvin)
Subject: Re: Gopher 1.02 problems
Organization: DSO, Stanford University
Date: 18 Aug 92 20:55:22 GMT

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.

"mike" (Mike Macgirvin)         Mike_Macgirvin@CAMIS.Stanford.EDU
Unix Server Administrator       CAMIS Computer Project
Newsgroups: comp.infosystems.gopher
From: jones@pyrite.cs.uiowa.edu (Douglas W. Jones,201H MLH,3193350740,3193382879)
Subject: Panda (Was: GopherCon ...)
Date: Tue, 18 Aug 1992 13:57:42 GMT
Organization: University of Iowa, Iowa City, IA, USA

From article <Bt5G8B.Itx@rice.edu>, by riddle@is.rice.edu (Prentiss Riddle):

> Lee Brintle from the University of Iowa's "panda" project talked about
> some of their extensive modifications to Gopher: ...
> The one Panda feature which seemed to gain everyone's approval was the
> ability to put explanatory text at the top and/or bottom of the screen
> rather than in an "About" file.

Indeed.  I was the first user of this feature, and I would not have used
Gopher/Panda had this feature not been available.  I put my course notes
on-line last spring using Panda, and without being able to add explanatory
text on the same screen as an index to my materials, I would have been
unable to present things in an organization clear enough to be worth using.

					Doug Jones
					jones@cs.uiowa.edu
From: snewton@oac.hsc.uth.tmc.edu (Steven E. Newton)
Newsgroups: comp.infosystems.gopher
Subject: Re: Problem searching with PC Gopher
Date: 19 Aug 1992 21:45:03 GMT
Organization: UT Health Science Center Houston

In article <thacker.56.714250799@cc1.unt.edu> thacker@cc1.unt.edu (Mark D. Thacker x2568) writes:
>In article <1992Aug19.000004.9502@talon.ucs.orst.edu> hanusj@bionette.cgrb.orst.edu (Joe Hanus) writes:
>>However my PC gopherII
>>1.04 fails to return any successful searches.  I get the "When I
>>looked, I didn't find anything" message.
[stuff deleted]
>>Any ideas for what is wrong?
>>
>
>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.

S.
-- 
+      +      +      +      +      +      +    |snewton@oac.hsc.uth.tmc.edu
         The map is the territory/             |Nobody else speaks for me,
       The map is not the territory.           |and I speak for no one else.
                                               |     +     +     +     +     +
Newsgroups: comp.infosystems.gopher