Mystic BBS Wiki

User Tools

Site Tools

Trace:
access_control

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
access_control [2016/03/22 12:13] – [ACS Function Reference] g00r00access_control [2021/06/23 09:01] – g00r00
Line 7: Line 7:
 Each ACS function is nothing more than a single character, most often followed by a parameter afterwards that supplements the function.  The most basic example of this would probably be an ACS of "s20".  An ACS of "s20" uses the function "S" which means security level, followed by 20, which defines is parameter.  The result of this ACS is that the user must have a security level of 20 or higher to have access. Each ACS function is nothing more than a single character, most often followed by a parameter afterwards that supplements the function.  The most basic example of this would probably be an ACS of "s20".  An ACS of "s20" uses the function "S" which means security level, followed by 20, which defines is parameter.  The result of this ACS is that the user must have a security level of 20 or higher to have access.
  
-In addition to this basic function and parameter system, ACS can use parenthesis to force an order of evaluation, and also has the typical Boolean operators AND OR NOT that can be used along with them.  Let's look at one example of a more complex ACS before we move on:+In addition to this basic function and parameter system, ACS can use parenthesis to force an order of evaluation, and also offers the typical Boolean operators AND OR NOT.  Let's look at one example of a more complex ACS before we move on:
  
      (s20!s21|s255)|u10|(h22!h23)      (s20!s21|s255)|u10|(h22!h23)
Line 39: Line 39:
                  example: DA will require the user to have user access flag                  example: DA will require the user to have user access flag
                  D in flag set 2 in order to pass.                  D in flag set 2 in order to pass.
-<code>+
           Ex  -  This command is used to check the user's current graphics           Ex  -  This command is used to check the user's current graphics
                  mode.  Where X is one of the following:                  mode.  Where X is one of the following:
 +     
                     1 - User must have ANSI graphics                     1 - User must have ANSI graphics
                     0 - User must have ASCII (none) graphics                     0 - User must have ASCII (none) graphics
-</code>+
           Fx  -  This command is used to check if a user has a certain flag           Fx  -  This command is used to check if a user has a certain flag
                  toggled ON in their FIRST set of flags.  Where X is the                  toggled ON in their FIRST set of flags.  Where X is the
Line 77: Line 77:
                  receive node messages, OA will return true.  False if                  receive node messages, OA will return true.  False if
                  they are not available.                  they are not available.
 +
 +          OC  -  This command is used to check if it is the user's first
 +                 call into the BBS.  OC will return true if it is the
 +                 first call.
  
           OI  -  This command is used to check if a user's node status           OI  -  This command is used to check if a user's node status
Line 100: Line 104:
                  false.  This option is useful to restrict users from                  false.  This option is useful to restrict users from
                  downloading if they're not active message posters.                  downloading if they're not active message posters.
 +
 +          OS  -  This command is true when the user is connected via a
 +                 securely encrypted connection to the BBS, such as SSH.
  
           OV  -  This command returns True if the user has validated their           OV  -  This command returns True if the user has validated their
access_control.txt · Last modified: 2024/03/03 03:20 by avon
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki