The kernel's get_random_bytes provides random numbers suitable for crypto
purposes, while in barebox, we need to use get_crypto_bytes for that.
This footgun needs to be fixed, but until we do, let's make sure crypto
code doesn't use a badly seeded PRNG.
Fixes: b62a31a9069b ("crypto: add new imx-scc driver")
Signed-off-by: Ahmad Fatoum <a.fat...@pengutronix.de>
---
drivers/crypto/imx-scc/scc-blobgen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/imx-scc/scc-blobgen.c
b/drivers/crypto/imx-scc/scc-blobgen.c
index 530d0840f810..a444386dab5a 100644
--- a/drivers/crypto/imx-scc/scc-blobgen.c
+++ b/drivers/crypto/imx-scc/scc-blobgen.c
@@ -67,7 +67,7 @@ static int imx_scc_blob_encrypt(struct blobgen *bg, const
char *modifier,
req.dst = blob;
req.nbytes = bufsiz;
- get_random_bytes(req.info, MAX_IVLEN);
+ get_crypto_bytes(req.info, MAX_IVLEN);
ret = imx_scc_cbc_des_encrypt(&req);
if (ret)
--
2.39.5
