Allow alternative backends for crypto provider
The crypto service provider is refactored to make it easy to add
alternative backends. There is still only a single backend that
uses the mbedcrypto library from MbedTLS. However, all dependencies
from the crypto provider on mbedcrypto have been removed, allowing
the crypto provider to be used with alternative implementations
of the PSA Crypto API.
Signed-off-by: Julian Hall <julian.hall@arm.com>
Change-Id: Ic5d1d9d47d149b634d147712749fdee48f260d85
diff --git a/deployments/env-test/env_test.cmake b/deployments/env-test/env_test.cmake
index ee46eba..a983b60 100644
--- a/deployments/env-test/env_test.cmake
+++ b/deployments/env-test/env_test.cmake
@@ -29,9 +29,9 @@
"components/service/test_runner/provider/serializer/packed-c"
"components/service/test_runner/provider/backend/null"
"components/service/test_runner/provider/backend/simple_c"
- "components/service/crypto/provider/mbedcrypto"
- "components/service/crypto/provider/mbedcrypto/trng_adapter/platform"
- "components/service/crypto/provider/mbedcrypto/trng_adapter/test"
+ "components/service/crypto/backend/mbedcrypto"
+ "components/service/crypto/backend/mbedcrypto/trng_adapter/platform"
+ "components/service/crypto/backend/mbedcrypto/trng_adapter/test"
"components/service/secure_storage/include"
"components/service/secure_storage/frontend/psa/its"
"components/service/secure_storage/backend/secure_storage_client"