Is there a plan to change the pseudo random number code from SHA-1 to SHA-2?

[nonark]

Regarding SHA-1 use, it is written in NIST as below.

NIST formally deprecated use of SHA-1 in 2011 and disallowed its use for digital signatures in 2013,
and declared that it should be phased out by 2030.

Is there any plan to add a pseudo-random code other than SHA-1

[juergw]

Conscrypt's implementation of SecureRandom doesn't really use SHA1, it only uses the name "SHA1PRNG" for compatibility
reasons, see comment here:
https://github.com/google/conscrypt/blob/master/common/src/main/java/org/conscrypt/OpenSSLProvider.java#L383

It uses "RAND_bytes" from BoringSSL:
https://github.com/google/conscrypt/blob/master/common/src/main/java/org/conscrypt/OpenSSLRandom.java

BoringSSL's RAND_bytes uses CTR-DRBG with AES-256 together with randomness from hardware.