[PATCH u-boot v2019.04-aspeed-openbmc 4/7] image: Check hash-nodes when checking configurations

Klaus Heinrich Kiwi klaus at linux.vnet.ibm.com
Fri Jan 29 08:30:17 AEDT 2021



On 1/28/2021 7:53 AM, Joel Stanley wrote:
> From: Simon Glass<sjg at chromium.org>
> 
> It is currently possible to use a different configuration's signature and
> thus bypass the configuration check. Make sure that the configuration node
> that was hashed matches the one being checked, to catch this problem.
> 
> Also add a proper function comment to fit_config_check_sig() and make it
> static.
> 
> Signed-off-by: Simon Glass<sjg at chromium.org>
> (cherry picked from commit 67acad3db71bb372458fbb8a77749f5eb88aa324)
> Signed-off-by: Joel Stanley<joel at jms.id.au>
Reviewed-by: Klaus Heinrich Kiwi <klaus at linux.vnet.ibm.com>

-- 
Klaus Heinrich Kiwi <klaus at linux.vnet.ibm.com>


More information about the openbmc mailing list