From: Stephen Warren <[email protected]> In real-world use-cases, hashing zero-length data likely never happens. However, it is relevant when testing cbootimage with a dummy zero-length bootloader binary, e.g.:
touch u-boot.bin cbootimage -t30 ../tamonten-ng/tegra30.img.cfg tegra30-tec-ng.img In this scenario, it's useful to create a consistent hash, so that one can compare the resultant images before and after applying patches, to check for regressions. Signed-off-by: Stephen Warren <[email protected]> --- src/crypto.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/crypto.c b/src/crypto.c index 88de357..9741785 100644 --- a/src/crypto.c +++ b/src/crypto.c @@ -183,6 +183,9 @@ sign_objext( if (enable_debug_crypto) print_vector("K1", KEY_LENGTH, k1); + if (!num_aes_blocks) + memset(dst, 0, 4 * NVAES_STATECOLS); + /* compute the AES-CMAC value */ for (i = 0; i < num_aes_blocks; i++) { /* Apply the chain data */ -- 1.8.1.5 -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
