Xref: utzoo comp.dcom.modems:10376 alt.bbs:5832 comp.org.eff.talk:2669
Path: utzoo!utgpu!cs.utexas.edu!wuarchive!uunet!aurs01!luce
From: luce@aurs01.UUCP (J. Luce)
Newsgroups: comp.dcom.modems,alt.bbs,comp.org.eff.talk
Subject: Re: USR Sysop Deal Change
Message-ID: <59920@aurs01.UUCP>
Date: 14 Jun 91 12:12:50 GMT
References: <2g1F43w163w@dorsai>
Sender: news@aurs01.UUCP
Reply-To: luce@aurps1.UUCP (J. Luce)
Organization: Alcatel Network Systems, Raleigh NC
Lines: 24

In article <2g1F43w163w@dorsai> 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.

They mean a list of the user log to see whow many users. Most BBSs give
the user a capability to see who the users are. If yours shows
EVERYTHING about the user, it is about time to change your s/w ;)

They do also browse the callerlog to see activity, but it is unimportant
other than to make sure you haven't been up for only a week.


-------------------------------------------------------------------
John Luce               | Life is the leading cause of death
Alcatel Network Systems | -----------------------------------------
Raleigh, NC             | Standard Disclaimer Applies
919-850-6787            | Mail? Here? Try aurs01!aurw46!luce@mcnc.org
                        |        or ...!mcnc!aurgate!luce
-------------------------------- or John.Luce@f130.n151.z1.fidonet.org