From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Luis Enriquez <lenriquez389@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
LUIS ENRIQUEZ <luis.enriquez@se.com>
Subject: Re: [OE-core] [PATCH] kernel-fitimage.bbclass: add padding algorithm property in config nodes
Date: Fri, 15 Jul 2022 10:11:38 +0200 [thread overview]
Message-ID: <YtEhOvYwdL+6CjY7@mail.local> (raw)
In-Reply-To: <20220713082802.581567-1-luis.enriquez@se.com>
Hello,
On 13/07/2022 10:28:03+0200, Luis Enriquez wrote:
> This allows choosing padding algorithm when building fitImage. It may be pkcs-1.5 or pss.
>
> Signed-off-by: LUIS ENRIQUEZ <luis.enriquez@se.com>
> From: LUIS ENRIQUEZ <lenriquez389@gmail.com>
> ---
> meta/classes/kernel-fitimage.bbclass | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/meta/classes/kernel-fitimage.bbclass b/meta/classes/kernel-fitimage.bbclass
> index 5f5e9dd444..7c0d93625b 100644
> --- a/meta/classes/kernel-fitimage.bbclass
> +++ b/meta/classes/kernel-fitimage.bbclass
> @@ -56,6 +56,9 @@ FIT_HASH_ALG ?= "sha256"
> # fitImage Signature Algo
> FIT_SIGN_ALG ?= "rsa2048"
>
> +# fitImage Padding Algo
> +FIT_PAD_ALG ?= "pkcs-1.5"
> +
> #
> # Emit the fitImage ITS header
> #
> @@ -250,6 +253,7 @@ fitimage_emit_section_config() {
>
> conf_csum="${FIT_HASH_ALG}"
> conf_sign_algo="${FIT_SIGN_ALG}"
> + conf_padding_algo="${FIT_PAD_ALG}"
> if [ "${UBOOT_SIGN_ENABLE}" = "1" ] ; then
> conf_sign_keyname="${UBOOT_SIGN_KEYNAME}"
> fi
> @@ -333,6 +337,7 @@ EOF
> signature-1 {
> algo = "${conf_csum},${conf_sign_algo}";
> key-name-hint = "${conf_sign_keyname}";
> + padding = "${conf_padding_algo}";
This doesn't apply on master, because of 2b5f5e295e9a ("featimage:
refactor style"). Can you rebase? Also, did you make sure you pass the
oe-selftest?
> ${sign_line}
> };
> EOF
> --
> 2.25.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167953): https://lists.openembedded.org/g/openembedded-core/message/167953
> Mute This Topic: https://lists.openembedded.org/mt/92328664/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-07-15 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 8:28 [PATCH] kernel-fitimage.bbclass: add padding algorithm property in config nodes LUIS ENRIQUEZ
2022-07-15 8:11 ` Alexandre Belloni [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-12 7:59 LUIS ENRIQUEZ
2022-07-12 20:55 ` [OE-core] " Alexandre Belloni
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=YtEhOvYwdL+6CjY7@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=lenriquez389@gmail.com \
--cc=luis.enriquez@se.com \
--cc=openembedded-core@lists.openembedded.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