Skip to content

RFC Anti rollback protection for FIT Images

Thirupathaiah Annapureddy u-boot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest0 of 1 patch 0 repliesNew

Patches in v1 No applies recorded yet

The patch the cover letter announces is not in this archive.

Reviews trailers per patch

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

Read the v1 thread

Cover letter [RFC PATCH 0/1] Anti rollback protection for FIT Images
Quoted 19 lines · Rasmus Villemoes
Quoted 9 lines · Rasmus Villemoes
Quoted 4 lines · Thirupathaiah Annapureddy

Anti rollback protection is required when there is a need to retire previous versions of FIT images due to security flaws in them. Currently U-Boot Verified boot does not have rollback protection to protect against known security flaws.

This is definitely something we've had on our todo-list/wishlist. But we haven't had the time to sit down and work out the semantics and implementation, so thanks for doing this.

...

Quoted 5 lines

The board callbacks would simply be given a pointer to the data part of that node; that would make the versioning scheme rather flexible instead of being limited to a single monotonically increasing u32 (hence also the comparison logic should be in the board callbacks, instead of a "get/set" interface).

Quoted 5 lines

Oh, and another reason for having the board callbacks being responsible for the Yay/Nay verdict is that that makes it possible to hook up a gpio that can be used to say "ignore rollback version check" - immensely useful during development, and might also come in handy for the end products.

This is not a good idea from security point of view as that would lead to physical present attacks.

Quoted 3 lines

Rasmus