All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Keeping <john@metanate.com>
To: u-boot@lists.denx.de
Subject: [PATCH] fit: Fix verification of images with external data
Date: Wed, 19 May 2021 14:47:39 +0100	[thread overview]
Message-ID: <20210519144739.5827d001.john@metanate.com> (raw)
In-Reply-To: <20210420181944.3945713-1-john@metanate.com>

On Tue, 20 Apr 2021 19:19:44 +0100
John Keeping <john@metanate.com> wrote:

> The "-E" option to mkimage generates a FIT with external data using the
> data-size and data-offset properties which must both be ignored when
> verifying a signature.
> 
> Add "data-offset" to the list of excluded properties for signature
> verification; since the line is now too long, re-format the list to
> one-per-line and make it static since the data is constant.
> 
> Signed-off-by: John Keeping <john@metanate.com>
> ---

Any feedback on this?  It would be nice to be able to verify all image
types produced by mkimage!


Thanks,
John

>  common/image-fit-sig.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/common/image-fit-sig.c b/common/image-fit-sig.c
> index 55ddf1879e..b979cd2a4b 100644
> --- a/common/image-fit-sig.c
> +++ b/common/image-fit-sig.c
> @@ -245,7 +245,13 @@ static int fit_config_check_sig(const void *fit, int noffset,
>  				int required_keynode, int conf_noffset,
>  				char **err_msgp)
>  {
> -	char * const exc_prop[] = {"data", "data-size", "data-position"};
> +	static char * const exc_prop[] = {
> +		"data",
> +		"data-size",
> +		"data-position",
> +		"data-offset"
> +	};
> +
>  	const char *prop, *end, *name;
>  	struct image_sign_info info;
>  	const uint32_t *strings;

  reply	other threads:[~2021-05-19 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 18:19 [PATCH] fit: Fix verification of images with external data John Keeping
2021-05-19 13:47 ` John Keeping [this message]
2021-05-19 15:34 ` Simon Glass
2021-08-05  1:18 ` Tom Rini

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=20210519144739.5827d001.john@metanate.com \
    --to=john@metanate.com \
    --cc=u-boot@lists.denx.de \
    /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.