Skip to content

Binman: fix signing an encrypted FIT with a

yan wang u-boot 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2tools: binman: Test signing an encrypted FIT with a preload headertools/binman/ftest.py tools/binman/test/336_pre_load_fit_encrypted.dts+80 -00 replies
2/2binman: Fix signing an encryted FIT with a preload keytools/binman/image.py+10 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] Binman: fix signing an encrypted FIT with a

When running the test case testPreLoadEncryptedFit, mkimage has been called multiple times. Each call to Entry_fit's GetData falls into Entry_fit's BuildSectionData then mkimage is called. The last mkimage is called after the image has been signed with the preload key. As mkimage uses a random IV for encryption and the timestamps may differ, There is a mismatch between the previously calculated signature and the final fit included in the image.

During ProcessImage, how can one tell when exactly a fit is well generated, and stop the useless mkimage afterwards?

Paul HENRYS (1):
tools: binman: Test signing an encrypted FIT with a preload header

yan wang (1):
binman: Fix signing an encryted FIT with a preload key

 tools/binman/ftest.py                         | 17 +++++
 tools/binman/image.py                         | 10 +++
 .../test/336_pre_load_fit_encrypted.dts       | 63 +++++++++++++++++++
 3 files changed, 90 insertions(+)
 create mode 100644 tools/binman/test/336_pre_load_fit_encrypted.dts
Signature · 1 line
2.25.1