<?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>49fcf732 - lockdown: Enforce module signatures if the kernel is locked down</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/lockdown/Kconfig#49fcf732</link>
        <description>lockdown: Enforce module signatures if the kernel is locked downIf the kernel is locked down, require that all modules have validsignatures that we can verify.I have adjusted the errors generated: (1) If there&apos;s no signature (ENODATA) or we can&apos;t check it (ENOPKG,     ENOKEY), then:     (a) If signatures are enforced then EKEYREJECTED is returned.     (b) If there&apos;s no signature or we can&apos;t check it, but the kernel is	 locked down then EPERM is returned (this is then consistent with	 other lockdown cases). (2) If the signature is unparseable (EBADMSG, EINVAL), the signature fails     the check (EKEYREJECTED) or a system error occurs (eg. ENOMEM), we     return the error we got.Note that the X.509 code doesn&apos;t check for key expiry as the RTC might notbe valid or might not have been transferred to the kernel&apos;s clock yet. [Modified by Matthew Garrett to remove the IMA integration. This will  be replaced with integration with the IMA architecture policy  patchset.]Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Signed-off-by: Matthew Garrett &lt;matthewgarrett@google.com&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Cc: Jessica Yu &lt;jeyu@kernel.org&gt;Signed-off-by: James Morris &lt;jmorris@namei.org&gt;

            List of files:
            /linux-6.15/security/lockdown/Kconfig</description>
        <pubDate>Tue, 20 Aug 2019 00:17:40 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>000d388e - security: Add a static lockdown policy LSM</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/security/lockdown/Kconfig#000d388e</link>
        <description>security: Add a static lockdown policy LSMWhile existing LSMs can be extended to handle lockdown policy,distributions generally want to be able to apply a straightforwardstatic policy. This patch adds a simple LSM that can be configured toreject either integrity or all lockdown queries, and can be configuredat runtime (through securityfs), boot time (via a kernel parameter) orbuild time (via a kconfig option). Based on initial code by DavidHowells.Signed-off-by: Matthew Garrett &lt;mjg59@google.com&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Cc: David Howells &lt;dhowells@redhat.com&gt;Signed-off-by: James Morris &lt;jmorris@namei.org&gt;

            List of files:
            /linux-6.15/security/lockdown/Kconfig</description>
        <pubDate>Tue, 20 Aug 2019 00:17:39 +0000</pubDate>
        <dc:creator>Matthew Garrett &lt;matthewgarrett@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
