linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: ming.lei@canonical.com
Cc: rusty@rustcorp.com.au, torvalds@linux-foundation.org,
	dhowells@redhat.com, seth.forshee@canonical.com,
	linux-kernel@vger.kernel.org, pebolle@tiscali.nl,
	linux-wireless@vger.kernel.org, gregkh@linuxfoundation.org,
	jlee@suse.com, tiwai@suse.de, casey@schaufler-ca.com,
	keescook@chromium.org, mjg59@srcf.ucam.org,
	akpm@linux-foundation.org, "Luis R. Rodriguez" <mcgrof@suse.com>
Subject: [RFC v3 0/2] firmware: add PKCS#7 firmware signature support
Date: Mon, 18 May 2015 17:45:23 -0700	[thread overview]
Message-ID: <1431996325-8840-1-git-send-email-mcgrof@do-not-panic.com> (raw)

From: "Luis R. Rodriguez" <mcgrof@suse.com>

This is the third iteration of RFCs for firmware signature suppport.
Upon review through discussions on the threads and IRC it seems folks are
generally OK with this now. This is rebased on top of David's latest pkcs7
branch but also depends on a series of patches which Rusty has said he
already applied but not yet visible on linux-next. It also has a series of
fixes posted by not yet in any tree nor has anyone claimed. Since the delta
is quite big in order to help folks review and test I've put up a branch
with all pending patches and requirements merged, you should use the
fw-signing-v3-20150518 branch on this tree:

https://git.kernel.org/cgit/linux/kernel/git/mcgrof/linux.git/

This is based on Linus' tree as base.

Changes on this v3 since the last v2 series:

  * Updated to David's latest pkcs7 branch
  * Dropped patches based on the above re-work
  * Avoid recommending use of scripts/sign-file to sign
    firmware as openssl can be used directly
  * Change expected file extension to be foo.bin.p7s, and
    update documentation to reflect this and how folks
    can let the kernel trust a key for fw signing.
  * Drop crypto qat work arounds - no longer needed

Luis R. Rodriguez (2):
  firmware: generalize reading file contents as a helper
  firmware: add firmware signature checking support

 Documentation/firmware_class/signing.txt |  90 ++++++++++++
 drivers/base/Kconfig                     |  18 +++
 drivers/base/firmware_class.c            | 236 +++++++++++++++++++++++++++++--
 3 files changed, 334 insertions(+), 10 deletions(-)
 create mode 100644 Documentation/firmware_class/signing.txt

-- 
2.3.2.209.gd67f9d5.dirty


             reply	other threads:[~2015-05-19  0:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  0:45 Luis R. Rodriguez [this message]
2015-05-19  0:45 ` [RFC v3 1/2] firmware: generalize reading file contents as a helper Luis R. Rodriguez
2015-05-19  0:45 ` [RFC v3 2/2] firmware: add firmware signature checking support Luis R. Rodriguez
2015-06-08 19:56   ` Kees Cook
2015-07-14 19:20     ` Luis R. Rodriguez
2015-07-21 23:14       ` Luis R. Rodriguez
2015-05-19  9:33 ` David Howells
2015-05-19 16:23   ` Luis R. Rodriguez
2015-05-19 10:02 ` David Howells
2015-05-19 16:31   ` Luis R. Rodriguez
2015-05-22 15:21 ` [RFC v3 0/2] firmware: add PKCS#7 firmware signature support David Howells

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=1431996325-8840-1-git-send-email-mcgrof@do-not-panic.com \
    --to=mcgrof@do-not-panic.com \
    --cc=akpm@linux-foundation.org \
    --cc=casey@schaufler-ca.com \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jlee@suse.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=ming.lei@canonical.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=pebolle@tiscali.nl \
    --cc=rusty@rustcorp.com.au \
    --cc=seth.forshee@canonical.com \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.org \
    /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).