From: Aditya Garg <gargaditya08@live.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: "jarkko@kernel.org" <jarkko@kernel.org>,
"dmitry.kasatkin@gmail.com" <dmitry.kasatkin@gmail.com>,
"jmorris@namei.org" <jmorris@namei.org>,
"serge@hallyn.com" <serge@hallyn.com>,
"ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"andrii@kernel.org" <andrii@kernel.org>,
"kafai@fb.com" <kafai@fb.com>,
"songliubraving@fb.com" <songliubraving@fb.com>,
"yhs@fb.com" <yhs@fb.com>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"kpsingh@kernel.org" <kpsingh@kernel.org>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"keyrings@vger.kernel.org" <keyrings@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Orlando Chamberlain <redecorating@protonmail.com>,
"admin@kodeit.net" <admin@kodeit.net>
Subject: Re: [PATCH v3 RESEND] efi: Do not import certificates from UEFI Secure Boot for T2 Macs
Date: Tue, 12 Apr 2022 15:40:57 +0000 [thread overview]
Message-ID: <E12D97B8-C609-4AA7-92E7-CE2A952089CD@live.com> (raw)
In-Reply-To: <2913e2998892833d4bc7d866b99dcd9bd234e82e.camel@linux.ibm.com>
> dmi_first_match() is called here at the beginning of load_uefi_certs().
> Only if it succeeds would uefi_check_ignore_db(), get_cert_list(),
> uefi_check_ignore_db(), or
> load_moklist_certs() be called. Is there a need for adding a call to
> dmi_first_match() in any of these other functions?
I’ll test this out.
>
> thanks,
>
> Mimi
>
>>>
>>> Like in all the other cases, there should be some sort of message. At
>>> minimum, there should be a pr_info().
>>>
>>>>
>>>> if (!efi_rt_services_supported(EFI_RT_SUPPORTED_GET_VARIABLE))
>>>> return false;
>>>
>
>
next prev parent reply other threads:[~2022-04-12 15:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 10:49 [PATCH v3 RESEND] efi: Do not import certificates from UEFI Secure Boot for T2 Macs Aditya Garg
2022-04-12 12:32 ` Mimi Zohar
2022-04-12 14:13 ` Aditya Garg
2022-04-12 15:13 ` Mimi Zohar
2022-04-12 15:40 ` Aditya Garg [this message]
2022-04-12 16:38 ` Aditya Garg
2022-04-12 16:40 ` [PATCH v4] " Aditya Garg
2022-04-12 16:44 ` [PATCH v4 RESEND] " Aditya Garg
2022-04-12 17:16 ` Mimi Zohar
2022-04-13 14:03 ` Aditya Garg
2022-04-13 14:04 ` [PATCH v5] " Aditya Garg
2022-04-14 13:30 ` Mimi Zohar
2022-04-15 6:17 ` Aditya Garg
2022-04-15 6:19 ` [PATCH v6] " Aditya Garg
2022-04-15 16:26 ` Mimi Zohar
2022-04-15 17:02 ` Aditya Garg
2022-04-15 17:02 ` [PATCH v7] " Aditya Garg
2022-04-22 17:39 ` [PATCH v7 RESEND] " Aditya Garg
2022-05-13 15:24 ` [PATCH v7] " Mimi Zohar
2022-05-13 18:31 ` Aditya Garg
2022-05-15 12:41 ` Mimi Zohar
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=E12D97B8-C609-4AA7-92E7-CE2A952089CD@live.com \
--to=gargaditya08@live.com \
--cc=admin@kodeit.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dmitry.kasatkin@gmail.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=keyrings@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=redecorating@protonmail.com \
--cc=serge@hallyn.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).