<?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 Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>d73ef9ec - loadpin: remove MODULE_COMPRESS_NONE as it is no longer supported</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#d73ef9ec</link>
        <description>loadpin: remove MODULE_COMPRESS_NONE as it is no longer supportedUpdated the MODULE_COMPRESS_NONE with MODULE_COMPRESS as it was no longeravailable from kernel modules. As MODULE_COMPRESS and MODULE_DECOMPRESSdepends on MODULES removing MODULES as well.Fixes: c7ff693fa209 (&quot;module: Split modules_install compression and in-kernel decompression&quot;)Signed-off-by: Arulpandiyan Vadivel &lt;arulpandiyan.vadivel@siemens.com&gt;Link: https://lore.kernel.org/r/20250302103831.285381-1-arulpandiyan.vadivel@siemens.comSigned-off-by: Kees Cook &lt;kees@kernel.org&gt;

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Sun, 02 Mar 2025 10:38:31 +0000</pubDate>
        <dc:creator>Arulpandiyan Vadivel &lt;arulpandiyan.vadivel@siemens.com&gt;</dc:creator>
    </item>
<item>
        <title>ce0d73ef - loadpin: Prevent SECURITY_LOADPIN_ENFORCE=y without module decompression</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#ce0d73ef</link>
        <description>loadpin: Prevent SECURITY_LOADPIN_ENFORCE=y without module decompressionIf modules are built compressed, and LoadPin is enforcing by default, wemust have in-kernel module decompression enabled (MODULE_DECOMPRESS).Modules will fail to load without decompression built into the kernelbecause they&apos;ll be blocked by LoadPin. Add a depends on clause toprevent this combination.Cc: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;Cc: Douglas Anderson &lt;dianders@chromium.org&gt;Signed-off-by: Stephen Boyd &lt;swboyd@chromium.org&gt;Link: https://lore.kernel.org/r/20240514224839.2526112-1-swboyd@chromium.orgSigned-off-by: Kees Cook &lt;keescook@chromium.org&gt;

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Tue, 14 May 2024 22:48:38 +0000</pubDate>
        <dc:creator>Stephen Boyd &lt;swboyd@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>6e42aec7 - LoadPin: Require file with verity root digests to have a header</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#6e42aec7</link>
        <description>LoadPin: Require file with verity root digests to have a headerLoadPin expects the file with trusted verity root digests to bean ASCII file with one digest (hex value) per line. A pinnedroot could contain files that meet these format requirements,even though the hex values don&apos;t represent trusted rootdigests.Add a new requirement to the file format which consists inthe first line containing a fixed string. This preventsattackers from feeding files with an otherwise valid formatto LoadPin.Suggested-by: Sarthak Kukreti &lt;sarthakkukreti@chromium.org&gt;Signed-off-by: Matthias Kaehlcke &lt;mka@chromium.org&gt;Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;Link: https://lore.kernel.org/r/20220906181725.1.I3f51d1bb0014e5a5951be4ad3c5ad7c7ca1dfc32@changeid

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Wed, 07 Sep 2022 01:18:12 +0000</pubDate>
        <dc:creator>Matthias Kaehlcke &lt;mka@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>aafc203b - LoadPin: Fix Kconfig doc about format of file with verity digests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#aafc203b</link>
        <description>LoadPin: Fix Kconfig doc about format of file with verity digestsThe doc for CONFIG_SECURITY_LOADPIN_VERITY says that the file with veritydigests must contain a comma separated list of digests. That was the caseat some stage of the development, but was changed during the reviewprocess to one digest per line. Update the Kconfig doc accordingly.Reported-by: Jae Hoon Kim &lt;kimjae@chromium.org&gt;Signed-off-by: Matthias Kaehlcke &lt;mka@chromium.org&gt;Fixes: 3f805f8cc23b (&quot;LoadPin: Enable loading from trusted dm-verity devices&quot;)Cc: stable@vger.kernel.orgSigned-off-by: Kees Cook &lt;keescook@chromium.org&gt;Link: https://lore.kernel.org/r/20220829174557.1.I5d202d1344212a3800d9828f936df6511eb2d0d1@changeid

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Tue, 30 Aug 2022 00:46:10 +0000</pubDate>
        <dc:creator>Matthias Kaehlcke &lt;mka@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>3f805f8c - LoadPin: Enable loading from trusted dm-verity devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#3f805f8c</link>
        <description>LoadPin: Enable loading from trusted dm-verity devicesExtend LoadPin to allow loading of kernel files from trusted dm-verity [1]devices.This change adds the concept of trusted verity devices to LoadPin. LoadPinmaintains a list of root digests of verity devices it considers trusted.Userspace can populate this list through an ioctl on the new LoadPinsecurityfs entry &apos;dm-verity&apos;. The ioctl receives a file descriptor ofa file with verity digests as parameter. Verity reads the digests fromthis file after confirming that the file is located on the pinned root.The digest file must contain one digest per line. The list of trusteddigests can only be set up once, which is typically done at boot time.When a kernel file is read LoadPin first checks (as usual) whether the fileis located on the pinned root, if so the file can be loaded. Otherwise, ifthe verity extension is enabled, LoadPin determines whether the file islocated on a verity backed device and whether the root digest of thatdevice is in the list of trusted digests. The file can be loaded if theverity device has a trusted root digest.Background:As of now LoadPin restricts loading of kernel files to a single pinnedfilesystem, typically the rootfs. This works for many systems, however itcan result in a bloated rootfs (and OTA updates) on platforms wheremultiple boards with different hardware configurations use the same rootfsimage. Especially when &apos;optional&apos; files are large it may be preferable todownload/install them only when they are actually needed by a given board.Chrome OS uses Downloadable Content (DLC) [2] to deploy certain &apos;packages&apos;at runtime. As an example a DLC package could contain firmware for aperipheral that is not present on all boards. DLCs use dm-verity to verifythe integrity of the DLC content.[1] https://www.kernel.org/doc/html/latest/admin-guide/device-mapper/verity.html[2] https://chromium.googlesource.com/chromiumos/platform2/+/HEAD/dlcservice/docs/developer.mdSigned-off-by: Matthias Kaehlcke &lt;mka@chromium.org&gt;Acked-by: Mike Snitzer &lt;snitzer@kernel.org&gt;Link: https://lore.kernel.org/lkml/20220627083512.v7.2.I01c67af41d2f6525c6d023101671d7339a9bc8b5@changeidSigned-off-by: Kees Cook &lt;keescook@chromium.org&gt;

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Mon, 27 Jun 2022 15:35:25 +0000</pubDate>
        <dc:creator>Matthias Kaehlcke &lt;mka@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>13523bef - LoadPin: Rename boot param &quot;enabled&quot; to &quot;enforce&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#13523bef</link>
        <description>LoadPin: Rename boot param &quot;enabled&quot; to &quot;enforce&quot;LoadPin&apos;s &quot;enabled&quot; setting is really about enforcement, not whetheror not the LSM is using LSM hooks. Instead, split this out so that LSMenabling can be logically distinct from whether enforcement is happening(for example, the pinning happens when the LSM is enabled, but the pinis only checked when &quot;enforce&quot; is set). This allows LoadPin to continueto operate sanely in test environments once LSM enable/disable iscentrally handled (i.e. we want LoadPin to be enabled separately fromits enforcement).Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;Reviewed-by: Casey Schaufler &lt;casey@schaufler-ca.com&gt;Reviewed-by: John Johansen &lt;john.johansen@canonical.com&gt;

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Mon, 24 Sep 2018 21:43:59 +0000</pubDate>
        <dc:creator>Kees Cook &lt;keescook@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>b937190c - LSM: LoadPin: provide enablement CONFIG</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#b937190c</link>
        <description>LSM: LoadPin: provide enablement CONFIGInstead of being enabled by default when SECURITY_LOADPIN is selected,provide an additional (default off) config to determine the boot timebehavior. As before, the &quot;loadpin.enabled=0/1&quot; kernel parameter remainsavailable.Suggested-by: James Morris &lt;jmorris@namei.org&gt;Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: James Morris &lt;james.l.morris@oracle.com&gt;

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Tue, 17 May 2016 08:45:52 +0000</pubDate>
        <dc:creator>Kees Cook &lt;keescook@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>9b091556 - LSM: LoadPin for kernel file loading restrictions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/loadpin/Kconfig#9b091556</link>
        <description>LSM: LoadPin for kernel file loading restrictionsThis LSM enforces that kernel-loaded files (modules, firmware, etc)must all come from the same filesystem, with the expectation thatsuch a filesystem is backed by a read-only device such as dm-verityor CDROM. This allows systems that have a verified and/or unchangeablefilesystem to enforce module and firmware loading restrictions withoutneeding to sign the files individually.Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;Acked-by: Serge Hallyn &lt;serge.hallyn@canonical.com&gt;Signed-off-by: James Morris &lt;james.l.morris@oracle.com&gt;

            List of files:
            /linux-6.15/security/loadpin/Kconfig</description>
        <pubDate>Wed, 20 Apr 2016 22:46:28 +0000</pubDate>
        <dc:creator>Kees Cook &lt;keescook@chromium.org&gt;</dc:creator>
    </item>
</channel>
</rss>
