You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → Posts by ThaPrintz
Pages 1
This is my user_settings file that wolfssl.lib is compiled with, and I am still getting these linker errors
So I recompiled with the preprocessors you mentioned, and everything seems to be working. However I am running into 1 issue, when trying to use HMAC 
I am getting these linker errors, and I have WOLFSSL_SHA3, WOLFSSL_SHA512 both defined, any ideas?
@ThaPrintz,
Thank you so much for reaching out with your questions.
Please try adding the settings to a custom user_settings.h and globally define WOLFSSL_USER_SETTINGS. At the application level you need to always include the <wolfssl/wolfcrypt/settings.h> before any other wolfSSL headers.
All other custom settings like user_settings.h should be included inside wolfssl/wolfcrypt/settings.h. user_settings.h is included in wolfssl/wolfcrypt/settings.h when WOLFSSL_USER_SETTINGS is defined globally.
Regards,
K
Kaleb,
Thanks for you response, however i do have WOLFSSL_USER_SETTINS globally defined, and i do have user_settings.h (this is where all my HAVE_MD2, HAVE_SHA256, etc etc are located).
I still get linker errors for:
MD2
Blake2B/S
poly1305
Camellia
HC128
ChaCha
RSA
All of the other cryptographic methods compile fine with no linker errors
I am currently working on a wrapper using wolfcrpypt, and im running into a a couple of problems and im not sure why.
1. I have wolfssl/wolfcrypt/Blake2B.h included, and i have the wolfssl static lib i compiled from the solution provided with the wolfssl download, and i am getting linker errors saying that the Init, Update, & Final Blake2B hashing funcs are unresolved.
2. Even though I have Blake2B.h included, I have to define HAVE_BLAKE2 and HAVE_BLAKE2B otherwise the functions wc_InitBlake2b, wc_Blake2bUpdate, and wc_Blake2bFinal are undefined,is this intentional? Because for MD4/5 and SHA/SHA256 I dont have to define anything for the funcs defined in the header to be recognized by VS, however with SHA224/SHA384/SHA512 and Blake2B/Blake2S I have to define the associated preprocessor definitions otherwise the functions are undefined when trying to call them
I actually figured out what i was doing wrong, on this line:
wsares = wolfSSL_read(this->csocket_ssl, buff, sizeof(buff));i accidentally used sizeof(); instead of strlen();
and considering i am compiling as 32bit the fact that sizeof(buff) is returning 3(really 4) bytes makes sense
For some reason im running into an issue where wolfSSL_read(); is reading data from the associated socket in chunks of 3, is this normal? Or is there something im doing wrong?
output
recv func
Pages 1
wolfSSL - Embedded SSL Library → Posts by ThaPrintz
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.018 seconds (96% PHP - 4% DB) with 4 queries