<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.linux.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>Linux Edu Handbook - ironpenguin</title>
        <description></description>
        <link>https://wiki.linux.edu/</link>
        <lastBuildDate>Sun, 26 Jul 2026 02:10:14 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://wiki.linux.edu/_media/wiki/dokuwiki.svg</url>
            <title>Linux Edu Handbook</title>
            <link>https://wiki.linux.edu/</link>
        </image>
        <item>
            <title>admin_capceiling</title>
            <link>https://wiki.linux.edu/ironpenguin/admin_capceiling?rev=1271359139&amp;do=diff</link>
            <description>capceiling with no arguments will display the current capabilities ceiling
capceiling (-|=)[ ]capability [capability...] &lt;program&gt;
run program with a reduced capability ceiling

The new ceiling is just a space delimited list of capabilities preceeded by either a '-' or '='</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:59 +0000</pubDate>
        </item>
        <item>
            <title>admin_fscap</title>
            <link>https://wiki.linux.edu/ironpenguin/admin_fscap?rev=1271359139&amp;do=diff</link>
            <description>'fscap'' is used to examine or set capabilities for an executable file.
fscap (+|-|=)[ ]forced-capability [forced-capability ...] [(+|-|=)[ ]allowed-capability [allowed-capability ...]] &lt;filename&gt;
'+': the capability list is added to allready set capabilities</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:59 +0000</pubDate>
        </item>
        <item>
            <title>admin_tools</title>
            <link>https://wiki.linux.edu/ironpenguin/admin_tools?rev=1271359139&amp;do=diff</link>
            <description>New system calls are all well and good, but are useless without something to call them.

IronPenguin features are utilized through a few new administrative tools:

capceiling is used to run a program with a lowered capability ceiling and to see the current ceiling.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:59 +0000</pubDate>
        </item>
        <item>
            <title>capabilities</title>
            <link>https://wiki.linux.edu/ironpenguin/capabilities?rev=1271359138&amp;do=diff</link>
            <description>POSIX Capabilities is a fundamentally sound idea hobbled by silliness that makes the capability system difficult to understand.

The idea behind POSIX capabilities is to replace the old model of root is god and everyone else isn't with the idea of a process having capabilities. Capabilities as defined in the POSIX draft may be seen as sub-divided root powers. For example, in the old model, root (UID 0) can bypass file permissions (that is, root is always permitted). In the capabilities model, if…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:58 +0000</pubDate>
        </item>
        <item>
            <title>capability_notes</title>
            <link>https://wiki.linux.edu/ironpenguin/capability_notes?rev=1271359137&amp;do=diff</link>
            <description>The IronPenguin capability system is almost but not quite the POSIX capability draft. The differences are the result of both a deeper analysis of the security considerations and of practical experiances form various POSIX systems attemption
to implement the POSIX draft, including the Linux kernel.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:57 +0000</pubDate>
        </item>
        <item>
            <title>capceiling</title>
            <link>https://wiki.linux.edu/ironpenguin/capceiling?rev=1271359137&amp;do=diff</link>
            <description>Capceiling is a new system call added by  in order to support jail and other security measures.

For i386 and x86_64 systems, it is defined as:
#define __NR_capceiling         318
_syscall1(int, capceiling, unsigned int *, capceiling);
or
int capceiling(unsigned int *caps);</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:57 +0000</pubDate>
        </item>
        <item>
            <title>dll_hell_for_the_21st_century</title>
            <link>https://wiki.linux.edu/ironpenguin/dll_hell_for_the_21st_century?rev=1271359138&amp;do=diff</link>
            <description>Just to be clear, this is NOT intended to be a rant against the existance of SELinux. There exist security environments where the amount of time and effort involved in properly maintaining an SELinux system is well justified and the various rollout delays are acceptable losses.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:58 +0000</pubDate>
        </item>
        <item>
            <title>jail_syscall</title>
            <link>https://wiki.linux.edu/ironpenguin/jail_syscall?rev=1271359138&amp;do=diff</link>
            <description>The jail call is inspired by and somewhat modeled on the jail syscall from FreeBSD. Jail brings together the IronPenguin improvements in chroot, bind mounts, etc and adds signal and process isolation.

The primary purpose of jail is to allow the creation of extremely lightweight virtual servers that live in a chroot jail.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:58 +0000</pubDate>
        </item>
        <item>
            <title>open_questions</title>
            <link>https://wiki.linux.edu/ironpenguin/open_questions?rev=1271359137&amp;do=diff</link>
            <description>The changes introduced in  open a few questions for security restrictions in the kernel.

	* Since the chroot system call can no longer be used to break out of a previous chroot, does it still need to be restricted to processes with CAP_SYS_CHROOT?
	*</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:57 +0000</pubDate>
        </item>
        <item>
            <title>prerequisits</title>
            <link>https://wiki.linux.edu/ironpenguin/prerequisits?rev=1271359139&amp;do=diff</link>
            <description>before you begin

Naturally, the first step is to upgrade to the IronPenguin kernel in the usual way.

To make full use of capabilities requires fscaps which, in turn, requires the filesystem to be mointed with the user_xattr option. For the usual case of an ext2 or ext3 filesystem,</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:59 +0000</pubDate>
        </item>
        <item>
            <title>start</title>
            <link>https://wiki.linux.edu/ironpenguin/start?rev=1271359137&amp;do=diff</link>
            <description>IronPenguin is a set of modifications to recent Linux kernels aimed at implementing both stronger and more versatile security functionality in Linux systems. 

IronPenguin is a quick hack that grew considerably in scope as time went on and it became clear just how much could be gained with a few well-considered small changes in the kernel.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 15 Apr 2010 19:18:57 +0000</pubDate>
        </item>
    </channel>
</rss>
