u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Thirupathaiah Annapureddy <thiruan@linux.microsoft.com>
To: u-boot@lists.denx.de
Subject: [PATCH v3 0/3] Add support for multiple required keys
Date: Sun, 16 Aug 2020 23:01:08 -0700	[thread overview]
Message-ID: <cover.1597643014.git.thiruan@linux.microsoft.com> (raw)

This patch series adds the support for multiple required keys
in U-Boot DTB with test support.

Changes in v3:
- Replaced 'u-boot' with 'U-Boot' in commit messages.
- Added an explicit print message to indicate that no required signature
was verified.

Changes in v2 (thanks for the feedback Simon and Rasmus):
- Introduce a policy variable in U-boot DTB to control whether any or all
required keys must have signed configuration.
- Added tests to cover any or all required keys policy. 
- Updated signature.txt to include required-mode policy information.

Thirupathaiah Annapureddy (3):
  vboot: add DTB policy for supporting multiple required conf keys
  test: vboot: add tests for multiple required keys
  doc: verified-boot: add required-mode information

 common/image-fit-sig.c       | 32 ++++++++++++++++++++++---
 doc/uImage.FIT/signature.txt | 14 +++++++++++
 test/py/tests/test_vboot.py  | 46 ++++++++++++++++++++++++++++++++++--
 3 files changed, 87 insertions(+), 5 deletions(-)

-- 
2.25.2

             reply	other threads:[~2020-08-17  6:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17  6:01 Thirupathaiah Annapureddy [this message]
2020-08-17  6:01 ` [PATCH v3 1/3] vboot: add DTB policy for supporting multiple required conf keys Thirupathaiah Annapureddy
2020-10-13 14:06   ` Tom Rini
2020-08-17  6:01 ` [PATCH v3 2/3] test: vboot: add tests for multiple required keys Thirupathaiah Annapureddy
2020-10-13 14:06   ` Tom Rini
2020-08-17  6:01 ` [PATCH v3 3/3] doc: verified-boot: add required-mode information Thirupathaiah Annapureddy
2020-10-13 14:06   ` Tom Rini

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=cover.1597643014.git.thiruan@linux.microsoft.com \
    --to=thiruan@linux.microsoft.com \
    --cc=u-boot@lists.denx.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;
as well as URLs for NNTP newsgroup(s).