All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Nie <jun.nie@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fit: skip signature verification if board request
Date: Wed, 18 Apr 2018 23:34:09 +0800	[thread overview]
Message-ID: <CABymUCNSoEmK0h398A_+8fbhp06Nz7ZGRjxt5KjN-J6YthS=xw@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ2rJ9xfTzFuv48gyWCvvJ=AOZPYMuoDXFCLua29o6b43Q@mail.gmail.com>

2018-04-17 3:06 GMT+08:00 Simon Glass <sjg@chromium.org>:
> Hi Jun,
>
> On 13 April 2018 at 04:05, Jun Nie <jun.nie@linaro.org> wrote:
>> 2018-04-13 1:24 GMT+08:00 Simon Glass <sjg@chromium.org>:
>>> Hi,
>>>
>>> On 11 April 2018 at 09:13, Jun Nie <jun.nie@linaro.org> wrote:
>>>> It may be unnecessary to check signature on unlocked board.
>>>> Get the hint from platform specific code to support secure boot
>>>> and non-secure boot with the same binary, so that boot is not
>>>> blocked if board is not locked and has no key for signature
>>>> verification.
>>>>
>>>> Signed-off-by: Jun Nie <jun.nie@linaro.org>
>>>> ---
>>>
>>> Instead of a weak function can you please add a parameter to this
>>> function (perhaps a flags word?) and a add test for this case to the
>>> test?
>>>
>>> Regards,
>>> Simon
>>
>> Sure, I can add a parameter to the function. But not sure what's the
>> usage of it in your mind. Maybe "int flag" is enough for you?
>
> Yes a flag is fine if you define an enum in the header file for that
> function. You will likely need to pass the flag around a few other
> functions.

I am still unclear on what the usage of this flag. I mean what variable
from fit_image_setup_verify() and fit_config_verify_required_sigs()
to be feed to this function as a flag. Maybe a void pointer is better
for different platform to pass context data and cost to specific data
structure. For example, pass data of image that to be verified.
fit_board_skip_sig_verification(const void *data)

>>
>> Do you mean add implementation of this function for a specific platform
>> for "add test"?
>
> See test/py/tests/test_vboot.py which you should be able to modify for
> your case.

Will check this file for more modification and test.

Thank you!

>
> Regards,
> Simon

  reply	other threads:[~2018-04-18 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 15:13 [U-Boot] [PATCH] fit: skip signature verification if board request Jun Nie
2018-04-12 13:53 ` Tom Rini
2018-04-13  9:58   ` Jun Nie
2018-04-12 17:24 ` Simon Glass
2018-04-13 10:05   ` Jun Nie
2018-04-16 19:06     ` Simon Glass
2018-04-18 15:34       ` Jun Nie [this message]
2018-04-17 12:06 ` Quentin Schulz
2018-04-18 15:22   ` Jun Nie

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='CABymUCNSoEmK0h398A_+8fbhp06Nz7ZGRjxt5KjN-J6YthS=xw@mail.gmail.com' \
    --to=jun.nie@linaro.org \
    --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.