22 Jul 97 21:10, Greg MacLellan wrote to Asher Densmore-Lynn:
 GM> to access any of that stuff on my system, you have to be a sysop PLUS
 GM> have a certain key. this means that even if someone is somehow put at
 GM> sysop, or if i upgrade their acess so they can download a file that's
 GM> not online, and forget about them, then they don't have complete sysop
 GM> access. I did the thing you have setup for a while, then i was at a
 GM> friends house trying to give them acess and couldn't since i couldn't
 GM> access the user editor, so that put an end to that =)
I thought of the key trick, but decided against it. Entering some, say, door 
game with SysOp access could allow a player to muck about with text files on 
a drive -- from there, they could probably have a key turned on for them at a 
menu or something without too much trouble.
(I'm a CoSys on a local Telegard board -- to prove a point, I created a 
filebase that pointed to his C:\ directory. He thought that I couldn't get 
out of the TG subtree, and -he- had read the docs; I just used guesswork. If 
he missed a trick, no reason I couldn't. Safer just to purge the whole 
shebang...)
I'm pursuing the idea that even if -my- password is compromised, it doesn't 
matter. There's a local low-level war going on -- nothing big; just keyboard 
capture programs, command stack peeking... Once I get this system running, I 
don't really intend to -use- it myself -- I can handle new-user apps from 
GoldEd -- may even make some macros for validation...
 I might even delete my SysOp account from the Max user files -- 
nah, that'd be going too far.
Asher Densmore-Lynn 
... GUI's, We have to use those extra Mhz's somehow!
--- Squish v1.11
---------------