All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] host-rauc: Allow use of host-libp11 for crypto hardware support
Date: Sun, 23 Jun 2019 18:04:29 +0200	[thread overview]
Message-ID: <20190623180429.5d600f1e@windsurf> (raw)
In-Reply-To: <20190223022338.5210-1-tpiepho@impinj.com>

On Sat, 23 Feb 2019 02:23:51 +0000
Trent Piepho <tpiepho@impinj.com> wrote:

> To use a private key stored on a hardware crypto module, such as an HSM
> or smart card, rauc needs OpenSSL to have support for pkcs11 modules.
> OpenSSL achieves this through the libp11 library.
> 
> The libp11 engine for OpenSSL is a dynamic module, so the dependency is
> at rauc's runtime, rather than openssl's or rauc's build time.  However,
> it still needs to be added as a dependency, so that anything that uses
> host-rauc when building can be assured that host-rauc is fully
> functional.
> 
> As this is a runtime dependency, there's no need for a target
> dependency.  And it's only used for signing updates, which isn't done on
> the target anyway.
> 
> Signed-off-by: Trent Piepho <tpiepho@impinj.com>
> ---
> To work, this requires the patch to add libp11, 
> https://patchwork.ozlabs.org/patch/1009607/

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-06-23 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23  2:23 [Buildroot] [PATCH] host-rauc: Allow use of host-libp11 for crypto hardware support Trent Piepho
2019-06-23 16:04 ` Thomas Petazzoni [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=20190623180429.5d600f1e@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.