For targets that support inclusion of the testfs, make sure to inject all config options needed to run the signature verification tests from the test_tlv.py which invoke the TLV command and verify some of the generated test TLVs against the builtin developer keys.
Signed-off-by: Jonas Rebmann <[email protected]> --- .github/workflows/test-labgrid-pytest.yml | 1 + common/boards/configs/enable_tlv_sig_testing.config | 13 +++++++++++++ 2 files changed, 14 insertions(+) diff --git a/.github/workflows/test-labgrid-pytest.yml b/.github/workflows/test-labgrid-pytest.yml index 4569e475bc..d9822fc206 100644 --- a/.github/workflows/test-labgrid-pytest.yml +++ b/.github/workflows/test-labgrid-pytest.yml @@ -89,6 +89,7 @@ jobs: if [ "${{ steps.used-features.outputs.testfs }}" = "true" ]; then KCONFIG_ADD="${KCONFIG_ADD} common/boards/configs/enable_dm_testing.config" + KCONFIG_ADD="${KCONFIG_ADD} common/boards/configs/enable_tlv_sig_testing.config" fi ./MAKEALL -O ${KBUILD_OUTPUT} -l "" -v 0 ${{matrix.defconfig}} diff --git a/common/boards/configs/enable_tlv_sig_testing.config b/common/boards/configs/enable_tlv_sig_testing.config new file mode 100644 index 0000000000..f1729fece5 --- /dev/null +++ b/common/boards/configs/enable_tlv_sig_testing.config @@ -0,0 +1,13 @@ +CONFIG_CRYPTO_BUILTIN_DEVELOPMENT_KEYS=y +CONFIG_CRYPTO_ECC=y +CONFIG_CRYPTO_RSA=y +CONFIG_CRYPTO_ECDSA=y +CONFIG_CRYPTO_BUILTIN_KEYS=y +CONFIG_CRYPTO_PUBLIC_KEYS="" +CONFIG_KEYTOC=y +CONFIG_TLV=y +CONFIG_TLV_DRV=y +CONFIG_TLV_BAREBOX=y +CONFIG_TLV_SIGNATURE=y +CONFIG_CMD_KEYS=y +CONFIG_CMD_TLV=y -- 2.51.2.535.g419c72cb8a
