From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [Next] package/kmod: modinfo support of signature details
Date: Fri, 15 May 2020 22:19:23 +0200 [thread overview]
Message-ID: <20200515201923.GF12536@scaer> (raw)
In-Reply-To: <20200514182806.56592-1-matthew.weber@rockwellcollins.com>
Matt, All,
On 2020-05-14 13:28 -0500, Matt Weber spake thusly:
> Add conditional support to allow the module tools to use openssl
> on target to inspect the signature of signed modules. If openssl
> is not enabled the modinfo will show a hash algo as unknown.
>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
Tested-by: Yann E. MORIN <yann.morin.1998@free.fr>
Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>
You tagged it for next, but I think we can see that as a fix, as it
at least ensures build order when enabled, and explicit disabling
otherwise.
Regards,
Yann E. MORIN.
> ---
> Prior to this patch the kmod series for compressed modules should
> be applied. No functionality dependency, I just identified them as
> patching conflicts.
>
> http://patchwork.ozlabs.org/project/buildroot/list/?series=174301
> ---
> package/kmod/kmod.mk | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/package/kmod/kmod.mk b/package/kmod/kmod.mk
> index 979c3e87e6..69615452cf 100644
> --- a/package/kmod/kmod.mk
> +++ b/package/kmod/kmod.mk
> @@ -46,6 +46,13 @@ else
> KMOD_CONF_OPTS += --without-xz
> endif
>
> +ifeq ($(BR2_PACKAGE_OPENSSL),y)
> +KMOD_DEPENDENCIES += openssl
> +KMOD_CONF_OPTS += --with-openssl
> +else
> +KMOD_CONF_OPTS += --without-openssl
> +endif
> +
> ifeq ($(BR2_PACKAGE_PYTHON)$(BR2_PACKAGE_PYTHON3),y)
> KMOD_DEPENDENCIES += $(if $(BR2_PACKAGE_PYTHON),python,python3)
> KMOD_CONF_OPTS += --enable-python
> --
> 2.17.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-05-15 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 18:28 [Buildroot] [Next] package/kmod: modinfo support of signature details Matt Weber
2020-05-15 20:19 ` Yann E. MORIN [this message]
2020-05-15 21:00 ` Yann E. MORIN
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=20200515201923.GF12536@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox