From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: mcgrof@kernel.org
Cc: rusty@rustcorp.com.au, dhowells@redhat.com,
ming.lei@canonical.com, seth.forshee@canonical.com,
kyle@kernel.org, David.Woodhouse@intel.com,
linux-kernel@vger.kernel.org,
AKASHI Takahiro <takahiro.akashi@linaro.org>
Subject: [PATCH 0/4] firmware: signature verification
Date: Fri, 26 May 2017 12:06:05 +0900 [thread overview]
Message-ID: <20170526030609.1414-1-takahiro.akashi@linaro.org> (raw)
This is my first version of patch series for adding signature
verification to firmware loading.
The original idea and code came from the work by Luis some time ago,
and I migrated it with some improvements to new driver data APIs,
leaving request_firmware() intact.
For details about how it works, please see the commit message of
patch#1 and the document under Documentation/driver-api/firmware.
Please note that patch#3, test script, is still a bit rough-edged,
especially that we have to prepare some data files in advance.
I will try to improve it for better automation.
For you convenience, the patch is available:
https://git.linaro.org/people/takahiro.akashi/linux-aarch64.git
firmware/signature
AKASHI Takahiro (4):
firmware: add firmware signing
scripts: sign-file: add firmware-signing option
test: firmwware: add signature test to driver_data loader test
firmware: document signature verification for driver data
Documentation/driver-api/firmware/driver_data.rst | 6 +
.../driver-api/firmware/fallback-mechanisms.rst | 5 +-
Documentation/driver-api/firmware/signing.rst | 81 +++++++
drivers/base/Kconfig | 25 ++
drivers/base/firmware_class.c | 211 +++++++++++++++-
include/linux/driver_data.h | 5 +
lib/test_driver_data.c | 56 ++++-
scripts/sign-file.c | 5 +-
tools/testing/selftests/firmware/driver_data.sh | 265 ++++++++++++++++++++-
9 files changed, 638 insertions(+), 21 deletions(-)
create mode 100644 Documentation/driver-api/firmware/signing.rst
--
2.11.1
next reply other threads:[~2017-05-26 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 3:06 AKASHI Takahiro [this message]
2017-05-26 3:06 ` [PATCH 1/4] firmware: add firmware signing AKASHI Takahiro
2017-05-30 16:07 ` Alan Cox
2017-05-26 3:06 ` [PATCH 2/4] scripts: sign-file: add firmware-signing option AKASHI Takahiro
2017-05-26 3:06 ` [PATCH 3/4] test: firmwware: add signature test to driver_data loader test AKASHI Takahiro
2017-05-26 3:06 ` [PATCH 4/4] firmware: document signature verification for driver data AKASHI Takahiro
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=20170526030609.1414-1-takahiro.akashi@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=David.Woodhouse@intel.com \
--cc=dhowells@redhat.com \
--cc=kyle@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ming.lei@canonical.com \
--cc=rusty@rustcorp.com.au \
--cc=seth.forshee@canonical.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).