core: fail build when CFG_INSECURE=n used with unsafe RNG seed

A production build needs a proper RNG seed. Fail the build when CFG_INSECURE=n is used in conjunction with the default weak stub implementation of plat_rng_init(). Signed-off-by: Sascha Hauer <[email protected]> Reviewed-by: Jerome Forissier <[email protected]> Reviewed-by: Jens Wiklander <[email protected]> Reviewed-by: Etienne Carriere <[email protected]>
gagachang · Feb 3, 2025 · fbffc8a · fbffc8a
1 parent fe33e97
commit fbffc8a
Showing 1 changed file with 7 additions and 0 deletions.
diff --git a/core/tee/tee_cryp_utl.c b/core/tee/tee_cryp_utl.c
@@ -200,7 +200,14 @@ void __plat_rng_init(void)
 	}
 }
 
+/*
+ * Override this in your platform code. This default implementation only seeds
+ * the random number generator from an easily predictable timestamp value or a
+ * constant value. It is not suitable for a secure environment.
+ */
+#ifdef CFG_INSECURE
 void plat_rng_init(void) __weak __alias("__plat_rng_init");
+#endif
 
 static TEE_Result tee_cryp_init(void)
 {