<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.rsbac.org/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="https://www.rsbac.org/feed.php">
        <title>RSBAC: Extending Linux Security Beyond the Limits documentation:rsbac_handbook:appendixes:rsbac_reference</title>
        <description></description>
        <link>https://www.rsbac.org/</link>
        <image rdf:resource="https://www.rsbac.org/lib/tpl/rsbac/images/favicon.ico" />
       <dc:date>2026-04-12T14:08:29+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/error_codes?rev=1231776623&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/kernel_parameters?rev=1258032176&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/proc_interface?rev=1286275726&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/targets_and_requests?rev=1231850105&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://www.rsbac.org/lib/tpl/rsbac/images/favicon.ico">
        <title>RSBAC: Extending Linux Security Beyond the Limits</title>
        <link>https://www.rsbac.org/</link>
        <url>https://www.rsbac.org/lib/tpl/rsbac/images/favicon.ico</url>
    </image>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/error_codes?rev=1231776623&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-12T16:10:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:appendixes:rsbac_reference:error_codes</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/error_codes?rev=1231776623&amp;do=diff</link>
        <description>Error Codes

RSBAC returns specific error codes on internal functions as well as RSBAC system calls. The following errors are defined:
Code    Reason  EPERM 	 Same as Linux EPERM: Permission denied.  EACCESS 	 RSBAC dir access failed internally  EREADFAILED</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/kernel_parameters?rev=1258032176&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-12T13:22:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:appendixes:rsbac_reference:kernel_parameters</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/kernel_parameters?rev=1258032176&amp;do=diff</link>
        <description>Kernel Boot Parameters

The RSBAC kernel accepts the following boot parameters:

General

	*  rsbac_no_defaults: suppress creation of default settings, useful for restore from existing backup. Warning: An unconfigured system will only come up in softmode or maint mode, and softmode will produce loads of logging (see rsbac_nosyslog option</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/proc_interface?rev=1286275726&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-05T10:48:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:appendixes:rsbac_reference:proc_interface</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/proc_interface?rev=1286275726&amp;do=diff</link>
        <description>proc Interface

If enabled in the kernel configuration, RSBAC adds one directory to the
main proc dir: /proc/rsbac-info. Since proc is treated as a normal read-only fs,
rsbac could not be used.

All successful write accesses are logged via syslog at KERN_INFO level.
The rsbac-info dir contains the following entries:</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/targets_and_requests?rev=1231850105&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-13T12:35:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:appendixes:rsbac_reference:targets_and_requests</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/appendixes/rsbac_reference/targets_and_requests?rev=1231850105&amp;do=diff</link>
        <description>Targets and Requests

RSBAC restricts access by subjects to objects. The subjects are always
processes, acting on the behalf of a user with certain attributes, like system_role etc.

Targets

Objects in RSBAC are called (Access) Targets. They are grouped in Target Types. The following types are defined:</description>
    </item>
</rdf:RDF>
