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
I call wc_InitSha384 before update and final every time I perform a hash.
Yes you are correct sizeof(input); is correct
No hardware acceleration. I'm using wolfssl-5.7.4-gplv3-fips-ready with the fipsv5 user_settings.h
Sorry that was just a typo by me. I am actually using sha384 as the variable used in init.
I probably don't understand how this works but my code is as follows:
byte input[] = {255};
byte hash[48];
wc_Sha384 sha384;
wc_InitSha384(&sha);
wc_Sha384Update(&sha384, input, sizeof(data));
wc_Sha384Final(&sha384, hash);
and then I'm checking the first 3 indices of hash against some hardcoded values.
I'm testing wc_InitSha384, wc_Sha384Update and wc_Sha384Final and I'm finding that my final hashed value is different every time I make a call. I'm hashing a byte array of 255, 255, 255 into a byte array of length 48 and it has different values every time. What gives?
I'm currently not using fast math in my user_settings.h. I've also found that defining WOLFSSL_STATIC_MEMORY causes wc_InitRsaKey to hang indefinitely.
Line 4862 in rsa.c seems to be the check that is causing things to fail.
What would be causing a MEMORY_E error during the initialization of an RSA key?
My user_settings.h defines related to RSA are:
WC_RSA_BLINDING
WC_RSA_PSS
USE_WOLFSSL_MEMORY
WOLFSSL_HAVE_SP_RSA
WOLFSSL_KEY_GEN
TARGET_EMBEDDED
If it helps I have also tried NO_MALLOC which causes the RSA initialization to hang indefinitely.
This on a Linux machine.
In the description of WolfCrypt it is stated that WolfCrypt is MISRA available. Does this mean there are versions that are MISRA compliant or that all versions of WolfCrypt are MISRA compliant? At the same time is WolfSSL MISRA compliant and what edition is it compliant to?
I've got --enable-cryptonly --disable-opensslextra set and wolfssl/ssl.h on line 2845 is still trying to include stdarg.h. What am I missing?
Okay I've made a bit of progress, but WolfSSL is still attempting to include stdarg.h when it is not available in ssl.h. Is there a way to disable this?
If I wanted to manually define INTEGRITY where would that go? I'm new to this so I'm doing a bit of bumbling.
I'm currently trying to get WolfSSL to build on the Integrity OS and beyond using
NO_FILESYSTEM
USER_TIME
USER_TICKS
I'm not sure what options I need to enable to get it to port over to Integrity?
Any ideas?
Posts found: 11
Generated in 0.014 seconds (96% PHP - 4% DB) with 4 queries