doc/uImage.FIT/signature.txt

6 FIT supports hashing of images so that these hashes can be checked on
112 - sign-images: A list of images to sign, each being a property of the conf
114 two images will be looked up in the config and signed if present.
121 	hashed-nodes = "/", "/configurations/conf@1", "/images/kernel@1",
122 		"/images/kernel@1/hash@1", "/images/fdt@1",
123 		"/images/fdt@1/hash@1";
128 Example: See sign-images.its for an example image tree source file and
153 "image" to force verification of all images, and "conf" to force verification
154 of the selected configuration (which then relies on hashes in the images to
170 While signing images is useful, it does not provide complete protection
172 FIT with the same signed images, but with the configuration changed such
180 	images {
242 With signed images, nothing protects against this. Whether it gains an
252 	images {
304 You can see that we have added hashes for all images (since they are no
307 pointed to by the configuration (/images/kernel@1, /images/kernel@1/hash@1,
308 /images/fdt@1, /images/fdt@1/hash@1) and the root structure of the image
318 of required images is produced. If there are 'required' public keys, then
333 WARNING: When relying on signed FIT images with required signature check
342 command loading and verifying images.
357 Build FIT with signed images
359 Sign images
360 Test Verified Boot Run: signed images: OK
363 Sign images
371 Build FIT with signed images
373 Sign images
374 Test Verified Boot Run: signed images: OK
377 Sign images
394 images which will appear genuine to your devices.