Re: [Suit] Introducing draft-moran-suit-manifest-04

[David Brown <[e-mail]>]

In regards to encrypting images.  I wanted to explain a little how
this works in MCUboot.

The basic process is similar to the swap described in:
https://www.youtube.com/watch?v=TvXjw2l0Cd0

However, the image in the secondary slot is always encrypted, and the
image in the primary slot is always unencrypted.  This makes an
assumption that the primary slot is more difficult to access (usually
an internal device), and that the secondary slot lives in an external
device.

The manifest is not changed when the image is moved between the slots
(and decrypted/encrypted).  Right now this logic is hard-coded into
MCUboot.  It would certainly be possible to keep it hard-coded, and
have the manifest describe both the encrypted and unencrypted payload
that MCUboot would then just know which one to use.

Note also that the primary image is re-encrypted when the swap
happens.  It uses the same IV for the encryption, which bothers me,
since it makes it slightly vulnerable to the plaintext being modified
(although if the plain text can be modified, many other attacks are
possible).

Any other thoughts on how to handle this?  BTW, this is not really
talking about encrypted payloads that are downloaded and decrypted
before being written to flash.  This is where there are two images in
flash, the executable one being unencrypted.