<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://wiki.synchro.net/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://wiki.synchro.net/feed.php">
        <title>Synchronet - access</title>
        <description></description>
        <link>http://wiki.synchro.net/</link>
        <image rdf:resource="http://wiki.synchro.net/_media/wiki:logo.png" />
       <dc:date>2026-04-10T08:50:50+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:credits?rev=1380794402&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:exemptions?rev=1519935698&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:flags?rev=1380793734&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:index?rev=1774229034&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:level?rev=1649030851&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:minutes?rev=1380794895&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:requirements?rev=1768289183&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:restrictions?rev=1738611047&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.synchro.net/access:sysop?rev=1752215973&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://wiki.synchro.net/_media/wiki:logo.png">
        <title>Synchronet</title>
        <link>http://wiki.synchro.net/</link>
        <url>http://wiki.synchro.net/_media/wiki:logo.png</url>
    </image>
    <item rdf:about="http://wiki.synchro.net/access:credits?rev=1380794402&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-03T10:00:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Credits</title>
        <link>http://wiki.synchro.net/access:credits?rev=1380794402&amp;do=diff</link>
        <description>Credits

Synchronet credits are a sort of monetary system whereby users can earn credits (e.g. by uploading files) and spend credits (e.g. by downloading files, playing games).

See Also

	*  Access Control

credits</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:exemptions?rev=1519935698&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-03-01T20:21:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Exemptions</title>
        <link>http://wiki.synchro.net/access:exemptions?rev=1519935698&amp;do=diff</link>
        <description>Exemptions

Exemptions are used by the sysop to give user&#039;s extended privilege
to the system. For example, you might want to give a trustworthy
user the right to remove, move, and edit descriptions of all files
in the File Transfer Section. Normally users can only remove or edit the
description of a file they&#039;ve uploaded, but a user with the</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:flags?rev=1380793734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-03T09:48:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Flags</title>
        <link>http://wiki.synchro.net/access:flags?rev=1380793734&amp;do=diff</link>
        <description>Flags

Security flags (or access flags) are like keys which the sysop can choose to give to specific users or groups of users and then require a user to possess one or more flags to access specific areas or features of the BBS (like placing a lock or locks on specific areas or features).</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:index?rev=1774229034&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-23T01:23:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Access Control</title>
        <link>http://wiki.synchro.net/access:index?rev=1774229034&amp;do=diff</link>
        <description>Access Control

Synchronet Access Control

Introduction

This topic covers a wide range of methods and instructions on how a Synchronet sysop can enable or restrict access to their BBS.

Host Filtering

Specific TCP/IP hosts (computers) or ranges of hosts can be restricted from accessing your Synchronet servers through the use of various</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:level?rev=1649030851&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-04-04T00:07:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Security Level</title>
        <link>http://wiki.synchro.net/access:level?rev=1649030851&amp;do=diff</link>
        <description>Security Level

Each user has an assigned security level. Levels 0 through 89 are for regular users, while level 90 through 99 are reserved for sysops and co-sysops.

Configuration

For each level (0-99), the sysop has defined limitations in SCFG-&gt;System</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:minutes?rev=1380794895&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-03T10:08:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Minutes</title>
        <link>http://wiki.synchro.net/access:minutes?rev=1380794895&amp;do=diff</link>
        <description>Minutes

Minutes can be banked by users for user later.

See Also

	*  Access Control

minutes</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:requirements?rev=1768289183&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-13T07:26:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Access Requirements</title>
        <link>http://wiki.synchro.net/access:requirements?rev=1768289183&amp;do=diff</link>
        <description>Access Requirements

Access Requirement Strings (ARS) are used to specify the requirements of a specific Synchronet user account in order to have access to specific areas or functions of a Synchronet BBS.

Overview

You will find in SCFG and other Synchronet</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:restrictions?rev=1738611047&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-03T19:30:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Restrictions</title>
        <link>http://wiki.synchro.net/access:restrictions?rev=1738611047&amp;do=diff</link>
        <description>Restrictions

A sysop can give a user restrictions from certain sections or features
of the BBS by setting one or more valid Restriction Flags.
 Flag         Name                    Description   A            ANSI and Ctrl-A Codes   User cannot write messages containing either</description>
    </item>
    <item rdf:about="http://wiki.synchro.net/access:sysop?rev=1752215973&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-07-11T06:39:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Sysop</title>
        <link>http://wiki.synchro.net/access:sysop?rev=1752215973&amp;do=diff</link>
        <description>Sysop

The sysop (System Operator) is the administrator that runs the BBS, and they have unlimited access and control over their instance of Synchronet and its users. When networked with other systems (e.g., DOVE-Net, FidoNet, inter-BBS chat), they are often considered responsible for any traffic originating from their system, including misconfigurations and any of their users&#039; poor behavior.</description>
    </item>
</rdf:RDF>
