From e1e4ae13b9c5fb9928c94e05f0fa5c17769fd5bd Mon Sep 17 00:00:00 2001 From: Jerome Forissier Date: Fri, 3 Nov 2023 10:41:57 +0100 Subject: [PATCH] TEE_Crypto_API.xml Disabling cases: - Invoke_Crypto_AllocateOperation_TEE_ALG_MD5_size_not_appropriate (3b-4d-15) - Invoke_Crypto_AllocateOperation_TEE_ALG_SHA1_size_not_appropriate (3b-86-3d) - Invoke_Crypto_AllocateOperation_TEE_ALG_SHA224_size_not_appropriate (3b-91-91) - Invoke_Crypto_AllocateOperation_TEE_ALG_SHA256_size_not_appropriate (3b-c6-3c) - Invoke_Crypto_AllocateOperation_TEE_ALG_SHA384_size_not_appropriate (3b-b0-94) - Invoke_Crypto_AllocateOperation_TEE_ALG_SHA512_size_not_appropriate (3b-f6-b8) These tests assume that TEE_AllocateOperation() must reject non-zero values for maxKeySize when the algorithm is MD5 or SHA (since the parameter is not applicable). But The GlobalPlatform TEE Internal Core API v1.1.2 has clarified the requirement, see: 6.2.1 TEE_AllocateOperation [...] The parameter maxKeySize MUST be a valid value as defined in Table 5-9 for the algorithm, for algorithms referenced in Table 5-9. For all other algorithms, the maxKeySize parameter may have any value. Link: https://github.com/OP-TEE/optee_os/pull/6416 Signed-off-by: Jerome Forissier --- packages/Crypto/xmlstable/TEE_Crypto_API.xml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/packages/Crypto/xmlstable/TEE_Crypto_API.xml b/packages/Crypto/xmlstable/TEE_Crypto_API.xml index b824637..b1cd7b0 100644 --- a/packages/Crypto/xmlstable/TEE_Crypto_API.xml +++ b/packages/Crypto/xmlstable/TEE_Crypto_API.xml @@ -149178,6 +149178,7 @@ + @@ -156360,6 +156362,7 @@ + @@ -156738,6 +156742,7 @@ + @@ -157116,6 +157122,7 @@ + @@ -157494,6 +157502,7 @@ + @@ -157872,6 +157882,7 @@ + -- 2.34.1