Synchronet Access Control
This topic covers a wide range of methods and instructions on how a Synchronet sysop can enable or restrict access to their BBS.
Specific TCP/IP hosts (computers) or ranges of hosts can be restricted from accessing your Synchronet servers through the use of various filter files. Filter files may also be used to restrict specific words from being used in user-generated content (message subjects, user names, aliases, etc.).
The sysop can disallow remote users from creating new user accounts by setting SCFG->System->Toggle Options->Closed To New Users to “Yes”.
The sysop can restrict users from creating new user accounts to only those that know a semi-secret New User Password (NUP), by setting SCFG->System->New User Password.
Synchronet user accounts each have the following security/access control settings which the sysop may use to enable or restrict the user's access to specific features of functions of the BBS:
The sysop determines which access control values will be assigned to newly created user accounts in SCFG->System->New User Values:
╔══════════════════════════════════════════════════════════╗ ║ New User Values ║ ╠══════════════════════════════════════════════════════════╣ ║ │Level 50 ║ ║ │Flag Set #1 ║ ║ │Flag Set #2 ║ ║ │Flag Set #3 ║ ║ │Flag Set #4 ║ ║ │Exemptions ║ ║ │Restrictions ║ ║ │Expiration Days 0 ║ ║ │Credits 10,485,760 ║ ║ │Minutes 0 ║ ║ │Editor FSEDITOR ║ ║ │Command Shell DEFAULT ║ ║ │Download Protocol None ║ ║ │Default Toggles... ║ ║ │Question Toggles... ║ ╚══════════════════════════════════════════════════════════╝
In the above example, newly created user accounts will have:
The sysop can specify combinations of access controls (e.g. security level, flags) and user values (e.g. gender, age, etc.) in SCFG (mostly under the options named “Access Requirements”) to control access to specific areas or functions of the BBS and restrict to specific groups of users.
See Access Requirements for more details.
There are multiple methods available for creating and editing user accounts:
;uedit
command from the main menu of the default command shellThe first user account created when connected to the Terminal server will automatically be given Sysop-level access (i.e., Security level 90, all flags and all exemptions).
For this reason, the System Password is prompted for (with the SY: prompt) during the first new user creation process.
The sysop account is traditionally the first user record in the database (i.e., user #1). This user account should not have the alias of “Sysop” - use your real name or a handle instead. Synchronet automatically treats the alias of Sysop specially and forwards any mail received for “Sysop” to user #1.
Some sysops will want to have a Guest
user account on their BBS. Guest accounts can be used to allow:
When a sysop with Security Level 99 logs into the Terminal server, they will be asked to create a Guest account if the following conditions are met:
Guest
user does not already existNo
and to not be asked again
If the sysop answers Yes
, the makeguest JavaScript module will be executed to create the Guest
account with the recommended access controls:
G, K, P, M, W, R, C
G, L, P, T
If you answered No
to both the “create Guest?” and “Ask again later?” prompts, you will need to run the makeguest.js module manually if you wish to create a Guest
account.