You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the IDF way in this case: We'll make "RNG" be "TRNG" by default, then provide function (revert_trng) to revert the "True" part and make it be just RNG again. However, it's not the most user-friendly approach, I'll think a bit more about other options.
On the other hand, having an explicit interface AND constructor for the TRNG is better then giving the "unsafe sword" to the user.
Feel free to post your thoughts here
The text was updated successfully, but these errors were encountered:
Copying from #1296 (comment)
Possible solutions:
revert_trng
for user, which is not a good solution from the point of "user-friendliness" (and many other points I guess)First one sounds a bit "hacky", third one sounds impossible/difficult.
IDF
seems to be using the second approach, which means thatrandom_disable
function is being provided to user "on his own risk" : https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/system/random.htmlI like the IDF way in this case: We'll make "RNG" be "TRNG" by default, then provide function (
revert_trng
) to revert the "True" part and make it be justRNG
again. However, it's not the most user-friendly approach, I'll think a bit more about other options.On the other hand, having an explicit interface AND constructor for the
TRNG
is better then giving the "unsafe sword" to the user.Feel free to post your thoughts here
The text was updated successfully, but these errors were encountered: