RSBAC has been tested and reported to be working with many Kernel options, other patches and separate software. Some of these are listed here. However, no warranty can be given that these reports are correct, or that the combination will work as expected on a given system.

This list will be extended whenever new reports come in.

RSBAC supports all kernel architectures. We don’t include any architecture specific code except kernel threads marking, but that’s just a one or two lines in assembler. Most of the tests were made on SMP.

Regular tests are made by ourselves on:

• i386 (main development platform)
• x86_64 (tested on AMD64)
• powerpc 32 bit (michal’s development platform, G4)

Other machines we were able to test RSBAC on:

• powerpc 64 bit (G5)
• alpha 64 bit
• sparc 32 bit and 64 bit
• s390 (native linux on zSeries)
• mips 64 bit kernel with 32 bit userland, big endian (keep in mind that every mips is in fact separate architecture. this test was made using SGI workstations.)

Positive test reports came in for:

• ia64
• s390 (31 Bit mode)
• sparc
• sparc64
• alpha
• arm

Please note that RSBAC is mostly filesystem independent and should thus work with any local filesystem. This list just shows those that have really been tested.

• ext2
• ext3
• xfs (without fs object hiding)
• reiserfs (without inode number checking and secure_delete)
• (v)fat (identification may be unreliable, see RSBAC kernel help)
• minix

RSBAC works with network filesystems too.

• SMP with fine locking
• loopback mounts, e.g. for encryption

• PaX (actively supported with RSBAC PAX module)
• Random Pid / Van Heusden
• FreeS/WAN
• OpenWall / GRSecurity (needs some hand patching)

• Xen (latest development versions only)
• Linux-VServer (with some hand patching)
• (Open)SSH
• libsafe
• X (if enabled in RSBAC kernel config)
• More generally, all software tested has been working successfully with RSBAC

Table of Contents: RSBAC Handbook
Previous: Areas of Use
Next chapter: Architecture and Implementation