From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: u-boot@lists.denx.de, Alexander Graf <agraf@csgraf.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH v2 0/6] efi_loader: fix secure boot mode transitions
Date: Fri, 27 Aug 2021 12:59:42 +0900 [thread overview]
Message-ID: <20210827035942.GD52912@laputa> (raw)
In-Reply-To: <20210826134805.148975-1-heinrich.schuchardt@canonical.com>
On Thu, Aug 26, 2021 at 03:47:59PM +0200, Heinrich Schuchardt wrote:
> The UEFI specification 2.9 defines the different modes that secure boot may
> be in.
>
> The patch series adds support for the "Deployed Mode" and the "Setup Mode".
This sentence seems to be wrong, or at least inaccurate.
"Setup Mode" has been supported from the beginning when I implemented
secure boot. In other word, I implemented only the transition between
"Setup Mode" and "User Mode" only.
-Takahiro Akashi
> Furthermore the secure boot signature database must only be loaded from
> tamper-resistant storage. So we must not load it from ubootefi.var on the
> EFI system partition but only from the preseed variables store or via the
> OP-TEE driver for the eMMC replay protected memory partition.
>
> v2:
> correct variable name in lib/efi_loader/efi_variable_tee.c
>
> Heinrich Schuchardt (6):
> efi_loader: stop recursion in efi_init_secure_state
> efi_loader: correct determination of secure boot state
> efi_loader: don't load signature database from file
> efi_loader: correct secure boot state transition
> efi_loader: writing AuditMode, DeployedMode
> efi_loader: always initialize the secure boot state
>
> include/efi_variable.h | 6 ++-
> lib/efi_loader/efi_var_common.c | 66 +++++++++++++++++++++++--------
> lib/efi_loader/efi_var_file.c | 41 +++++++++++--------
> lib/efi_loader/efi_variable.c | 20 ++++++----
> lib/efi_loader/efi_variable_tee.c | 4 +-
> 5 files changed, 95 insertions(+), 42 deletions(-)
>
> --
> 2.30.2
>
prev parent reply other threads:[~2021-08-27 3:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 13:47 [PATCH v2 0/6] efi_loader: fix secure boot mode transitions Heinrich Schuchardt
2021-08-26 13:48 ` [PATCH v2 1/6] efi_loader: stop recursion in efi_init_secure_state Heinrich Schuchardt
2021-08-27 2:26 ` AKASHI Takahiro
2021-08-26 13:48 ` [PATCH v2 2/6] efi_loader: correct determination of secure boot state Heinrich Schuchardt
2021-08-26 13:48 ` [PATCH v2 3/6] efi_loader: don't load signature database from file Heinrich Schuchardt
2021-08-27 4:12 ` AKASHI Takahiro
2021-08-27 4:42 ` Heinrich Schuchardt
2021-08-27 4:49 ` AKASHI Takahiro
2021-08-27 4:51 ` AKASHI Takahiro
2021-08-27 5:22 ` Heinrich Schuchardt
2021-08-26 13:48 ` [PATCH v2 4/6] efi_loader: correct secure boot state transition Heinrich Schuchardt
2021-08-26 13:48 ` [PATCH v2 5/6] efi_loader: writing AuditMode, DeployedMode Heinrich Schuchardt
2021-08-27 3:05 ` AKASHI Takahiro
2021-08-27 4:09 ` Heinrich Schuchardt
2021-08-27 9:23 ` Ilias Apalodimas
2021-08-26 13:48 ` [PATCH v2 6/6] efi_loader: always initialize the secure boot state Heinrich Schuchardt
2021-08-27 3:53 ` AKASHI Takahiro
2021-08-27 4:34 ` Heinrich Schuchardt
2021-08-27 4:47 ` AKASHI Takahiro
2021-08-27 4:53 ` Heinrich Schuchardt
2021-08-27 3:59 ` AKASHI Takahiro [this message]
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=20210827035942.GD52912@laputa \
--to=takahiro.akashi@linaro.org \
--cc=agraf@csgraf.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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