Hi,

I let you notify that  ’INDIVIDUAL_SW_COMPONENTS’ support is planned to be removed from attestation service and bootloader.

What is this?

• Boootloader and SPE can exchange data through shared memory. This is needed to provide the boot status info to attestation service. The boot status info is included in the SW_COMPONENT claim in the attestation token.
• Until now two types of data encoding was supported during this data sharing:
• All boot status data item is passed as a single TLV entry:  -DATTEST_BOOT_INTERFACE=INDIVIDUAL_CLAIMS
• Boot status is already encoded to CBOR format at build time. Bootloader only updates a few field in it, and pass the CBOR object to SPE. Then attestation service just include this already CBOR formatted object to the token, without the need to applying further encoding.

-DATTEST_BOOT_INTERFACE=CBOR_ENCODED_CLAIMS

The  ‘INDIVIDUAL_CLAIMS’ format is marked as deprecated feature for a while in the code base. Now the plan is to remove it and rely fully on the ‘CBOR_ENCODED_CLAIMS’ format.

The build system support for this is present in TF-M for a long, and recently it was upstream to original MCUBoot ‘imgtool’ script as well. Next MCUBoot release (v1.6) will contain it.

If you has any objection, because your project  is using the ’INDIVIDUAL_CLAIMS’ format then please let us know!

BR,

Tamas