TIP: Click on subject to list as thread! ANSI
echo: muffin
to: Gert Koefoed Andersen
from: Bob Jones
date: 2006-05-07 12:11:30
subject: Maximus and msgAreas permissions

GKA> I could make some extra answers in a newuser file 
 GKA> there ask the user about he is node i some nets and 
 GKA> ask him to type the node number and if the user type 
 GKA> no to the first net then jump to next nets.

You could set up the initial log in script (mex file?) to handle asking the
questions.  

 GKA> When the user has type in his node number maximus then 
 GKA> look into the nodelist for checking it and if the name 
 GKA> is find here the file set the first key for the user 
 GKA> and if more than one nets several keys is sets for the 
 GKA> user and each msg area has this keys so if it goes 
 GKA> like this:

You would need some external process / program to validate the nodelist
information.  I believe that is reasonable to do....

 GKA> 1. Is you a Starnet node (Yes/No) ?
 GKA>    Your node number here :
 GKA> 2. Is you a Linuxnet node (Yes/No)
 GKA>    Your node number :
 ...

Reasonable.....

 GKA> And each answer of yes and by in typing the right node 
 GKA> mumber will set the keys for the user such as like all 
 GKA> 6 has a Yes answer gives keys as 578CFG +something other keys.
 GKA> then could i in the msgs setup use divisions where it 
 GKA> could be like each nets msgarea starnet.* etc. and 
 GKA> divison is starnet and the user is by the question and 
 GKA> his answer setup for the nets as starnet linuxnet stn 
 GKA> etc. so when he goes to the msg areas will see the msg 
 GKA> from start of.

You have the right idea.  I probably would manually set the keys when I
validated the user.....

 GKA> In the msgarea.ctl file shall have made the nets Style 
 GKA> and acs setup with higher levels and keys and maybe 
 GKA> use setup by divisions like:
 GKA> MsgDivisionsBegin linuxnet     Demoted . DIVISIONS: Linuxnet
 GKA> MsgArea sysops
 GKA>     ACS     Demoted
 GKA>     Desc     (LN) Sysop echo
 GKA>     Style   Squish Conf Pub Pvt
 GKA>     Tag     linuxnet.sysops
 GKA>     Path    ........
 GKA> End MsgArea
 ...

You have the right idea.  I believe the keys need to be specified with the
access level.  From memory, the MsgDivisionBegin line should contain
something like Demoted/L and the ACS line for the linuxnet.sysops area
should also have Demoted/L if key L is what you are using for Linuxnet.  If
the key is set for the user, the user will see the area *if* they have
privilage of Demoted or greater.  If the key is *not* set, they would not
see the area at all.

 GKA> So when the user has the right keys setup for the nets 
 GKA> and msgs he will could see and use the msgs when he 
 GKA> goes to msg section and the keys are set to be make it 
 GKA> the user just like to see the linuxnet echo he type 
 GKA> linuxnet and get all the echoes for linuxnet and not 
 GKA> other echoes.

You have the correct idea......

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)
SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848
@PATH: 343/41 138/146 392 123/500 261/38 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.