From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libp11: Add new package for OpenSSL PKCS#11 engine
Date: Sat, 6 Apr 2019 13:57:44 +0200 [thread overview]
Message-ID: <20190406135744.747367a3@windsurf> (raw)
In-Reply-To: <CAKON4Ozg+dp1j5BwTOVemKmpL-e+Hmw9E+MPeM7n+drqaiV53g@mail.gmail.com>
Hello Jon,
On Fri, 5 Apr 2019 15:29:03 -0400
"jonsmirl at gmail.com" <jonsmirl@gmail.com> wrote:
> I managed to get libp11 working with this makefile. The previous problems I
> encountered were fixed by a full rebuild of my tree. I needed libp11
> because we are using the ATECC608A for securely accessing with AWS IOT. It
> also works with Google and Azure.
> https://github.com/MicrochipTech/cryptoauthlib/wiki/PKCS11-Linux-Setup
There is already a libp11 package in Buildroot, I merged the patch that
was contributed by Trent Piepho a few days ago:
https://git.buildroot.org/buildroot/commit/package/libp11?id=c4fc706f556c80046bf5cba93b1964c376c71208
> ################################################################################
> #
> # cryptoauthlib
> #
However, we don't have this package in Buildroot. Could you submit a
proper patch adding it, so that we can do a review and hopefully merge
it ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-06 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 18:13 [Buildroot] [PATCH v2] libp11: Add new package for OpenSSL PKCS#11 engine Trent Piepho
2018-12-29 5:36 ` Frank Hunleth
2018-12-31 20:10 ` Trent Piepho
2019-04-04 19:45 ` Thomas Petazzoni
2019-04-04 21:10 ` Trent Piepho
2019-04-05 7:49 ` Thomas Petazzoni
2019-04-05 17:57 ` Trent Piepho
2019-04-05 19:29 ` jonsmirl at gmail.com
2019-04-06 11:57 ` Thomas Petazzoni [this message]
2019-04-06 14:39 ` jonsmirl at gmail.com
2019-04-26 8:12 ` Thomas Petazzoni
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=20190406135744.747367a3@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.