eb49d927a5
Sometimes, it may be desired that the DEY project does not sign the artifacts, for example, if they are going to be externally signed on a secure server. In this case, the user sets TRUSTFENCE_SIGN="0". On STM platforms, all the variables were being set if TRUSTFENCE_SIGN="1" and authentication support is not enabled on TF_A otherwise. Set TF_A_SIGN_ENABLE (which adds authentication support to TF_A) always for STM platforms (as long as the project inherits the trustfence class) and set FIP_SIGN_ENABLE="0" if its sibling TRUSTFENCE_SIGN="0", so that DEY doesn't sign the FIP image either. Signed-off-by: Hector Palacios <hector.palacios@digi.com> |
||
|---|---|---|
| .. | ||
| aws-iot.bbclass | ||
| dey-image-installer.bbclass | ||
| dey-image.bbclass | ||
| populate_sdk_qt6.bbclass | ||
| qt-version.bbclass | ||
| trustfence.bbclass | ||