You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work for ASSA ABLOY, and we've been utilizing SUIT since draft 4 in a straightforward manner. I'm now exploring ways to expand our implementation to support additional sub-specifications and make broader use of sequences and directives. I have a few questions, but I'll start with one that's been puzzling me the most.
I'm interested in adding support for dependency manifests, the multi-trust domains specification, and the firmware encryption specification. According to the main SUIT specification, the only required command sequence is suit-validate.
However, when I look at the example in the Firmware Encryption specification here, it only includes the suit-install command, which is optional, and does not mention the required suit-validate.
Am I missing something?
The text was updated successfully, but these errors were encountered:
Hi
I work for ASSA ABLOY, and we've been utilizing SUIT since draft 4 in a straightforward manner. I'm now exploring ways to expand our implementation to support additional sub-specifications and make broader use of sequences and directives. I have a few questions, but I'll start with one that's been puzzling me the most.
I'm interested in adding support for dependency manifests, the multi-trust domains specification, and the firmware encryption specification. According to the main SUIT specification, the only required command sequence is suit-validate.
However, when I look at the example in the Firmware Encryption specification here, it only includes the suit-install command, which is optional, and does not mention the required suit-validate.
Am I missing something?
The text was updated successfully, but these errors were encountered: