-
Notifications
You must be signed in to change notification settings - Fork 835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RX72N support update #7849
RX72N support update #7849
Conversation
Retest this please. client failed! Suite = DHE-RSA-AES128-SHA256 version = 3 |
wolfcrypt/src/random.c
Outdated
@@ -3655,15 +3652,6 @@ int wc_GenerateSeed(OS_Seed* os, byte* output, word32 sz) | |||
return 0; | |||
} | |||
|
|||
#elif defined(WOLFSSL_RENESAS_TSIP) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't want this removed. I added it back for a customer in ZD 18222. The TSIP RNG comes out of a CTR-DRBG but there is no issue using it as a seed for our DRBG. If a customer wants to use it directly then they can still define CUSTOM_RAND_GENERATE_BLOCK
to override our DRBG and use wc_tsip_GenerateRandBlock
directly.
comment to CUSTOM RAND GENERATE BLOCK
Added comment to |
Revert 2b4acf5
Fix compile failure when no TSIP uses
Description
TSIP random generator is not true random generator, but it generates pseudo random based on AES CTR-DRBG. So, it needs to use CUSTOM_RAND_GENERATE_BLOCK.
fix build failure when no using TSIP
this fixes zd#18415(#4 item, TIME_OVERRIDES define)
zd#18415
Testing
Run RX72N example programs
Checklist