<?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</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-28T09:00:25+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/administration_examples/syslog-ng?rev=1147881195&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/administration_examples/syslog-ng?rev=1146577225&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/maintenance/upgrade_and_migration?rev=1231759121&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/setting_up_modules/cap?rev=1231849962&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/acronyms?rev=1146577225&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/installation/first_boot?rev=1231760307&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/security_models/acl?rev=1231840383&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/security_models/vum?rev=1204198894&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/setting_up_modules/daz?rev=1238676446&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/configuration_basics/administration_examples/syslog-ng?rev=1147881195&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-05-17T15:53:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:configuration_basics:administration_examples:syslog-ng</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/administration_examples/syslog-ng?rev=1147881195&amp;do=diff</link>
        <description>Setting Up syslog-ng Logging

You can use syslog-ng to log RSBAC log messages, which is much more convenient.
Disable logging to system log with the “rsbac_nosyslog” kernel flag, or
echo “debug nosyslog 1” &gt; /proc/rsbac-info/debug at runtime.
You need the kernel option</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/administration_examples/syslog-ng?rev=1146577225&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-05-02T13:40:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:administration_examples:syslog-ng</title>
        <link>https://www.rsbac.org/documentation/administration_examples/syslog-ng?rev=1146577225&amp;do=diff</link>
        <description>You can use syslog-ng to log RSBAC log messages.

Setting up syslog-ng

Disable logging to system log with the “rsbac_nosyslog” kernel flag, or
echo “debug nosyslog 1” &gt; /proc/rsbac-info/debug at runtime.
You need the kernel option “CONFIG_RSBAC_RMSG_NOSYSLOG</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/maintenance/upgrade_and_migration?rev=1231759121&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-12T11:18:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:maintenance:upgrade_and_migration</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/maintenance/upgrade_and_migration?rev=1231759121&amp;do=diff</link>
        <description>About RSBAC upgrades

This document covers the upgrade steps to be followed after each major RSBAC release. If you missed some major upgrade and directly upgrade to the last RSBAC release, you can scroll down and find the changes that will affect you during your upgrade process.</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/setting_up_modules/cap?rev=1231849962&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-13T12:32:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:configuration_basics:setting_up_modules:cap</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/setting_up_modules/cap?rev=1231849962&amp;do=diff</link>
        <description>Setting up CAP

Before starting with Linux Capabilities (CAP) module administration, your should read the CAP description.

CAP administration only change min_caps and max_caps attributes of users and files. This can either be done with rsbac_user_menu and rsbac_fd_menu or with the command line tools attr_get_user, attr_set_user, attr_get_file_dir and attr_set_file_dir.</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/acronyms?rev=1146577225&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-05-02T13:40:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:acronyms</title>
        <link>https://www.rsbac.org/documentation/acronyms?rev=1146577225&amp;do=diff</link>
        <description>Acronyms

There are many, many different acronyms in projects such as RSBAC. This page lists the most important ones, directly or not directly related to RSBAC

Note that you often have acronyms underlined in the website. By moving your mouse cursor over them, you can get a direct description.</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/installation/first_boot?rev=1231760307&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-12T11:38:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:installation:first_boot</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/installation/first_boot?rev=1231760307&amp;do=diff</link>
        <description>Preparing your boot loader

You will need a few special options for you first RSBAC boot.
If you need, we have a complete (and extensive) list of kernel parameters.

When you boot, the default RSBAC policy will disallow any setuid call. It means you will not be able to log in!
To alleviate this, you can tell RSBAC at boot time that we allow</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/security_models/acl?rev=1231840383&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-13T09:53:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:security_models:acl</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/security_models/acl?rev=1231840383&amp;do=diff</link>
        <description>Access Control Lists (ACL)

Access Control Lists specify, which subject (user, RC role or ACL group) may access which object (of an object type) with which requests (usual RSBAC requests and ACL specials).

If there is no ACL entry for a subject at an object, the rights of the parent object are inherited. Inheritance can be restricted by inheritance masks.</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/security_models/vum?rev=1204198894&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-28T11:41:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:security_models:vum</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/security_models/vum?rev=1204198894&amp;do=diff</link>
        <description>Virtual User Management

Design

Starting from version 1.4, RSBAC contains Virtual User Management (VUM), which is an extension to the existing User Management (UM).

Every user id now consists of a 32 Bit virtual set (vset) number and the old fashioned 32 Bit uid. The normal set of users is vset 0. It also exists, if VUM has been turned off in kernel configuration. All other vset numbers can be used as desired, there is no list of known sets.</description>
    </item>
    <item rdf:about="https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/setting_up_modules/daz?rev=1238676446&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-02T12:47:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation:rsbac_handbook:configuration_basics:setting_up_modules:daz</title>
        <link>https://www.rsbac.org/documentation/rsbac_handbook/configuration_basics/setting_up_modules/daz?rev=1238676446&amp;do=diff</link>
        <description>Setting up DAZ

Dazuko is an interface for Antivirus scanners. In this document we will use the ClamAV scanner to connect with the Dazuko interface provided by the RSBAC DAZ module.

Preparing your system

First of all, make sure the DAZ module is selected, compiled and active in your RSBAC kernel.</description>
    </item>
</rdf:RDF>
