From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 4/4] linux-yocto: use openssl-native.bbclass
Date: Tue, 4 Oct 2022 14:28:12 +0300 [thread overview]
Message-ID: <YzwYzKYCeoBYpIQF@nuoska> (raw)
In-Reply-To: <e0fc2054236524ba2cca50068503089aaaf72c08.camel@linuxfoundation.org>
Hi,
On Tue, Oct 04, 2022 at 11:44:51AM +0100, Richard Purdie wrote:
> On Tue, 2022-10-04 at 13:11 +0300, Mikko Rapeli wrote:
> > It sets environment variables etc correctly for openssl-native use.
> > For most kernel side use cases are covered by plain openssl native
> > wrapper but some out of tree e.g. python scripts may be not.
>
> When you say "out of tree", you mean scripts in the kernel we don't use
> by default, or scripts that aren't in the kernel at all but some users
> add?
Both. Same for u-boot which has internal signing scripts that require
python3-cryptography-native which doesn't work out of the box.
> I'd have thought the dependency on the class would be added where it
> was being used?
Yes, this could be done too, but I'd like to set a clear example in poky
by using this bbclass.
The root causes are not obvious when ../usr/bin/openssl works but
../usr/lib/libcrypto.so doesn't.
Cheers,
-Mikko
prev parent reply other threads:[~2022-10-04 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 10:11 [PATCH 4/4] linux-yocto: use openssl-native.bbclass Mikko Rapeli
2022-10-04 10:44 ` [OE-core] " Richard Purdie
2022-10-04 11:28 ` Mikko Rapeli [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=YzwYzKYCeoBYpIQF@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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).