You are not logged in. Please login or register.
Active topics Unanswered topics
Welcome to the wolfSSL Forums!
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
References
Stable Releases - download stable product releases.
Development Branch - latest development branch on GitHub.
wolfSSL Manual - wolfSSL (formerly CyaSSL) product manual and API reference.
Search options
Hello Kareem,
Thank you for your response! I am using the MSPM0 platform and based on what you said, I think I have to use the TRNG api's in the SDK. Would this mean I have to compile wolfssl with a custom header file which provides a function to use the TRNG instructions for the library?
Thank you again!
Hello, I’m relatively new to embedded systems and security, so I appreciate your patience. I am developing a secure file system in a bare metal platform, and for that I am using some encryption algorithms that use a RNG. To initialize the RNG, I used the wc_InitRng function. However, when testing, I received an error relating to the initialization of the RNG. Here, I remembered that my platform does not have an OS. I figured out that it supports RNG through it's hardware (TRNG). This led me to believe that the issue may be related to how wolfSSL expects RNG sources to be configured in a bare-metal environment. However, I couldn't figure out how that can be done.
My question is: How can I configure wolfSSL to use my platform’s hardware TRNG instead of the default RNG implementation?
Any guidance or examples would be greatly appreciated.
Thank you!
Posts found: 2
Generated in 0.008 seconds (53% PHP - 47% DB) with 5 queries