<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in object.h</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>06a1c40a - landlock: Format with clang-format</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/landlock/object.h#06a1c40a</link>
        <description>landlock: Format with clang-formatLet&apos;s follow a consistent and documented coding style.  Everything maynot be to our liking but it is better than tacit knowledge.  Moreover,this will help maintain style consistency between different developers.This contains only whitespace changes.Automatically formatted with:clang-format-14 -i security/landlock/*.[ch] include/uapi/linux/landlock.hLink: https://lore.kernel.org/r/20220506160513.523257-3-mic@digikod.netCc: stable@vger.kernel.orgSigned-off-by: Micka&#235;l Sala&#252;n &lt;mic@digikod.net&gt;

            List of files:
            /linux-6.15/security/landlock/object.h</description>
        <pubDate>Fri, 06 May 2022 16:05:08 +0000</pubDate>
        <dc:creator>Micka&#235;l Sala&#252;n &lt;mic@digikod.net&gt;</dc:creator>
    </item>
<item>
        <title>90945448 - landlock: Add object management</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/landlock/object.h#90945448</link>
        <description>landlock: Add object managementA Landlock object enables to identify a kernel object (e.g. an inode).A Landlock rule is a set of access rights allowed on an object.  Rulesare grouped in rulesets that may be tied to a set of processes (i.e.subjects) to enforce a scoped access-control (i.e. a domain).Because Landlock&apos;s goal is to empower any process (especiallyunprivileged ones) to sandbox themselves, we cannot rely on asystem-wide object identification such as file extended attributes.Indeed, we need innocuous, composable and modular access-controls.The main challenge with these constraints is to identify kernel objectswhile this identification is useful (i.e. when a security policy makesuse of this object).  But this identification data should be freed onceno policy is using it.  This ephemeral tagging should not and may not bewritten in the filesystem.  We then need to manage the lifetime of arule according to the lifetime of its objects.  To avoid a global lock,this implementation make use of RCU and counters to safely referenceobjects.A following commit uses this generic object management for inodes.Cc: James Morris &lt;jmorris@namei.org&gt;Signed-off-by: Micka&#235;l Sala&#252;n &lt;mic@linux.microsoft.com&gt;Reviewed-by: Jann Horn &lt;jannh@google.com&gt;Acked-by: Serge Hallyn &lt;serge@hallyn.com&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Link: https://lore.kernel.org/r/20210422154123.13086-2-mic@digikod.netSigned-off-by: James Morris &lt;jamorris@linux.microsoft.com&gt;

            List of files:
            /linux-6.15/security/landlock/object.h</description>
        <pubDate>Thu, 22 Apr 2021 15:41:11 +0000</pubDate>
        <dc:creator>Micka&#235;l Sala&#252;n &lt;mic@linux.microsoft.com&gt;</dc:creator>
    </item>
</channel>
</rss>
