Xref: utzoo comp.dcom.modems:10360 alt.bbs:5813 comp.org.eff.talk:2652
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!hub.ucsb.edu!piggy!jim
From: jim@piggy.ucsb.edu (Jim Lick)
Newsgroups: comp.dcom.modems,alt.bbs,comp.org.eff.talk
Subject: Re: USR Sysop Deal Change
Message-ID: <12075@hub.ucsb.edu>
Date: 14 Jun 91 00:19:39 GMT
References: <2g1F43w163w@dorsai>
Sender: news@hub.ucsb.edu
Lines: 21

bigd@dorsai (David Shapiro) writes:
>In the latest (June) issue of Boardwatch magazine, it says that the USR 
>sysop deal has been changed, which a clause stating that USR "must be able 
>to view all files and user log in order to validate board staus...."
>Do they really mean *user* log, or did someone mess up and mistake a user 
>log, which contains, among other things, every users information and 
>password, including the sysop's, for a caller's log, which contains just a
>record of who's called and done what.

I took it to mean what you thought.  To me, user log means a list of users.
Maybe even a last called column.  What you think of a user log, I would
call a password file.  I imagine that this policy is because of people 
wanting cheap modems and setting up a BBS on their PC to get it.

                            Jim Lick		       
Work: University of California	| Home: 6657 El Colegio #24
      Santa Barbara		|       Isla Vista, CA 93117-4280
      Dept. of Mechanical Engr. |	(805) 968-0189 voice/msg
      2311 Engr II Building     |	(805) 968-1239 data 
      (805) 893-4113            |	(805) 968-2734 fax
      jim@ferkel.ucsb.edu	|	Soon: jim@cave.sba.ca.us