Page MenuHomePhabricator

Some PSA-Arch Crypto tests fail with CC-312
Closed, WontfixPublic

Description

The expected test result summary should be this:

Crypto Suite Report **
TOTAL TESTS : 61
TOTAL PASSED : 39
TOTAL SIM ERROR : 0
TOTAL FAILED : 21
TOTAL SKIPPED : 1


But the test result summary is:

Crypto Suite Report **
TOTAL TESTS : 61
TOTAL PASSED : 37
TOTAL SIM ERROR : 0
TOTAL FAILED : 23
TOTAL SKIPPED : 1


Test environment is:

ConfigPsaApiTest, ARMCLANG & GNUARM, Minsizerel, musca_b1_OTP.
ConfigPsaApiTestIPC & ConfigPsaApiTestIPCTfmLevel2, ARMCLANG, Minsizerel, musca_b1_OTP.

Event Timeline

Update from Tamas

"
The two extra failing test case (TEST 241 and TEST 242) is the same which was failing in case of RC3. It's a known limitations of the CC312 crypto library: MD hashing is not supported.


Logs from TF-Mv1.0-RC3 test with enabled CC312 on Musca-B1:


TEST: 241 | DESCRIPTION: Testing crypto asymmetric APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_asymmetric_sign - RSA KEYPAIR PKCS1V15 RAW

DVIR: ERROR: MBEDTLS_MD_NONE is not supported!
Failed at Checkpoint: 6
Actual: -135
Expected: 0
TEST RESULT: FAILED (Error Code=0x1)


TEST: 242 | DESCRIPTION: Testing crypto asymmetric APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_asymmetric_verify - RSA KEYPAIR PKCS1V15 RAW
Failed at Checkpoint: 6
Actual: -135
Expected: 0
TEST RESULT: FAILED (Error Code=0x1)


Logs from TF-Mv1.0 test with enabled CC312 on Musca-B1:

TEST: 241 | DESCRIPTION: Testing crypto asymmetric APIs

[Info] Executing tests from non-secure

[Check 1] Test psa_asymmetric_sign - RSA KEY_PAIR PKCS1V15 RAW

DVIR: ERROR: MBEDTLS_MD_NONE is not supported!
Failed at Checkpoint: 4

Actual: -135

Expected: 0

TEST RESULT: FAILED (Error Code=0x00000001)


TEST: 242 | DESCRIPTION: Testing crypto asymmetric APIs

[Info] Executing tests from non-secure

[Check 1] Test psa_asymmetric_verify - RSA KEY_PAIR PKCS1V15 RAW

Failed at Checkpoint: 4

Actual: -135

Expected: 0

TEST RESULT: FAILED (Error Code=0x00000001)
"

Known limitation of CC312 crypto library. It does not require any further investigation.

soby-mathew closed this task as Wontfix.Wed, Mar 25, 10:24 AM

This is a known limitation of CC-312 and hence will not be fixed in TF-M code.