linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: R Nageswara Sastry <rnsastry@linux.ibm.com>
To: Nayna Jain <nayna@linux.ibm.com>, linux-integrity@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Eric Snowberg <eric.snowberg@oracle.com>,
	Paul Moore <paul@paul-moore.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-security-module@vger.kernel.org,
	inux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/6] integrity: ignore keys failing CA restrictions on non-UEFI platform
Date: Wed, 16 Aug 2023 20:11:01 +0530	[thread overview]
Message-ID: <eb595d1d-bc9f-8451-9450-cb1c4a02ce9b@linux.ibm.com> (raw)
In-Reply-To: <20230815112722.1591829-3-nayna@linux.ibm.com>



On 15/08/23 4:57 pm, Nayna Jain wrote:
> On non-UEFI platforms, handle restrict_link_by_ca failures differently.
> 
> Certificates which do not satisfy CA restrictions on non-UEFI platforms
> are ignored.
> 
> Signed-off-by: Nayna Jain <nayna@linux.ibm.com>
> Reviewed-and-tested-by: Mimi Zohar <zohar@linux.ibm.com>
> Acked-by: Jarkko Sakkinen <jarkko@kernel.org>


Tested with trustedcadb, moduledb scenarios
Tested-by: Nageswara R Sastry <rnsastry@linux.ibm.com>

> ---
>   security/integrity/platform_certs/machine_keyring.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/security/integrity/platform_certs/machine_keyring.c b/security/integrity/platform_certs/machine_keyring.c
> index 7aaed7950b6e..389a6e7c9245 100644
> --- a/security/integrity/platform_certs/machine_keyring.c
> +++ b/security/integrity/platform_certs/machine_keyring.c
> @@ -36,7 +36,7 @@ void __init add_to_machine_keyring(const char *source, const void *data, size_t
>   	 * If the restriction check does not pass and the platform keyring
>   	 * is configured, try to add it into that keyring instead.
>   	 */
> -	if (rc && IS_ENABLED(CONFIG_INTEGRITY_PLATFORM_KEYRING))
> +	if (rc && efi_enabled(EFI_BOOT) && IS_ENABLED(CONFIG_INTEGRITY_PLATFORM_KEYRING))
>   		rc = integrity_load_cert(INTEGRITY_KEYRING_PLATFORM, source,
>   					 data, len, perm);
>   

-- 
Thanks and Regards
R.Nageswara Sastry

  reply	other threads:[~2023-08-16 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 11:27 [PATCH v4 0/6] Enable loading local and third party keys on PowerVM guest Nayna Jain
2023-08-15 11:27 ` [PATCH v4 1/6] integrity: PowerVM support for loading CA keys on machine keyring Nayna Jain
2023-08-16 14:40   ` R Nageswara Sastry
2023-08-16 20:34   ` Jarkko Sakkinen
2023-08-15 11:27 ` [PATCH v4 2/6] integrity: ignore keys failing CA restrictions on non-UEFI platform Nayna Jain
2023-08-16 14:41   ` R Nageswara Sastry [this message]
2023-08-15 11:27 ` [PATCH v4 3/6] integrity: remove global variable from machine_keyring.c Nayna Jain
2023-08-16 14:41   ` R Nageswara Sastry
2023-08-15 11:27 ` [PATCH v4 4/6] integrity: check whether imputed trust is enabled Nayna Jain
2023-08-16 14:41   ` R Nageswara Sastry
2023-08-15 11:27 ` [PATCH v4 5/6] integrity: PowerVM machine keyring enablement Nayna Jain
2023-08-16 14:42   ` R Nageswara Sastry
2023-08-15 11:27 ` [PATCH v4 6/6] integrity: PowerVM support for loading third party code signing keys Nayna Jain
2023-08-15 20:30   ` Mimi Zohar
2023-08-16 14:42   ` R Nageswara Sastry
2023-08-16 20:36   ` Jarkko Sakkinen
2023-08-16 21:06     ` Mimi Zohar
2023-08-16 21:11       ` Jarkko Sakkinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb595d1d-bc9f-8451-9450-cb1c4a02ce9b@linux.ibm.com \
    --to=rnsastry@linux.ibm.com \
    --cc=eric.snowberg@oracle.com \
    --cc=inux-kernel@vger.kernel.org \
    --cc=jarkko@kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nayna@linux.ibm.com \
    --cc=paul@paul-moore.com \
    --cc=zohar@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).