From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Jimmy Zhang <jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [cbootimage PATCH v6 1/5] Add support for update pubkey and rsa-pss signatures
Date: Mon, 19 Oct 2015 14:38:29 -0600 [thread overview]
Message-ID: <562554C5.1010504@wwwdotorg.org> (raw)
In-Reply-To: <1445281385-28020-2-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 10/19/2015 01:03 PM, Jimmy Zhang wrote:
> Create new configuration keywords:
> RsaKeyModulusFile: pubkey modulus
> RsaPssSigBlFile: bootloader rsa pss signature
> RsaPssSigBctFile: bct rsa pss signature
>
> Sample Configuration file update_bl_sig.cfg
> RsaKeyModulusFile = pubkey.mod;
> RsaPssSigBlFile = bl.sig;
>
> where pubkey.mod and bl.sig are files that contain the public key
> modulus and bootloader's rsa-pss signature respectively.
>
> public key modulus and signature are created through utilities
> outside cbootimage.
>
> Command line example:
> $ cbootimage -s tegra210 -u update_bl_sig.cfg image.bin image.bin-bl-signed
>
> Above three new keywords added in this CL are only implemented to support
> for T210.
>
> Changes in V6:
> 1) Rename function swap_endianness() to reverse_byte_order()
> 2) Put "size - 1 - i" to a variable to avoid double calculation
> 3) Remove checking NULL pointer of get_value_size() in function set_rsa_param()
> 4) Change function prototype for get_value_size()
The changelog should be below the --- line since it's not typically
checked in.
> src/t114/nvbctlib_t114.c | 1 +
> src/t124/nvbctlib_t124.c | 1 +
> src/t210/nvbctlib_t210.c | 46 +++++++++++++++++++++++++++++++++++++++++++++-
t20, t30, t132 files should be updated to add an implementation of
struct cbootimage_soc_config .get_value_size too.
I was going to apply these patches and then send a patch to fix that up,
but I noticed that this series introduces a bunch of warnings. Can you
submit v7 that builds cleanly, has that fixed, and:
> diff --git a/src/crypto.c b/src/crypto.c
> +void
> +reverse_byte_order(
> + u_int8_t *out,
> + u_int8_t *in,
"in" should be const.
next prev parent reply other threads:[~2015-10-19 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:03 [cbootimage PATCH v6 0/5] Add RSA signing support Jimmy Zhang
[not found] ` <1445281385-28020-1-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-10-19 19:03 ` [cbootimage PATCH v6 1/5] Add support for update pubkey and rsa-pss signatures Jimmy Zhang
[not found] ` <1445281385-28020-2-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-10-19 20:38 ` Stephen Warren [this message]
[not found] ` <562554C5.1010504-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-10-19 22:50 ` Jimmy Zhang
2015-10-19 19:03 ` [cbootimage PATCH v6 2/5] Add support to dump rsa related fields for t210 Jimmy Zhang
2015-10-19 19:03 ` [cbootimage PATCH v6 3/5] Add new configuration keyword "RehashBl" Jimmy Zhang
2015-10-19 19:03 ` [cbootimage PATCH v6 4/5] Add a sample script to do rsa signing for T210 bootimage Jimmy Zhang
2015-10-19 19:03 ` [cbootimage PATCH v6 5/5] Bump to version 1.6 Jimmy Zhang
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=562554C5.1010504@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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