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 (Page 5 of 15)
Hi wangzihao,
You'll want to pass in the the curve ID to wc_ecc_get_generator:
ret = wc_ecc_get_generator(pt, wc_ecc_get_curve_idx(ECC_SECP256R1));
There is an example in test_wc_ecc_get_generator() in tests/api.c
Thanks,
Eric - wolfSSL Support
Hi avlec,
I recommend sending an email to our support team. It will be easier for us to make suggestions if we first gather your version and config information.
support@wolfssl.com
Thanks,
Eric
Hello alex65,
Thanks for joining the wolfSSL Forums. Usually an undefined error indicates that the component you are trying use is not configured
in wolfSSL. Please check that the following macro is defined
Here are instructions for changing the configuration:
https://github.com/wolfSSL/wolfssl/tree … figuration
Thanks,
Eric - wolfSSL Support
Hello cvinothkumar,
Thanks for joining the wolfSSL Forums. You'll want to use wc_PKCS12_parse to get the DER cert out of the bundle.
https://github.com/wolfSSL/wolfssl-exam … -example.c
Then you can retrieve the public key from the DER cert
https://github.com/wolfSSL/wolfssl-exam … m-certfile
Could you tell us a bit about your project?
Thanks,
Eric - wolfSSL Support
Hi testwolverinebagel,
Thanks for joining the wolfSSL Forums. That is odd. Is this on an embedded platform that may be delayed while trying to negotiate a secure connection?
I will check with the team to see if we have a wolfSSH example client set up with EPOLL that you could review.
Kind regards,
Eric - wolfSSL Support
Hi muataz.m
Could you tell us a bit about your project?
Have you reviewed the Android example readme?
https://github.com/wolfSSL/wolfssljni/t … DE/Android
Let us know if that helps.
Thanks,
Eric - wolfSSL Support
I am answering your questions via the support ticket you opened in our ZenDesk portal
You can use the configuration define
Excellent, we'll continue the conversation there!
Hi vschiavoni,
Thanks for joining the wolfSSL Forums. Yes, we are still gathering requirements for the project. Please send an email to
and we can have a discussion about your use case.
Kind regards,
Eric - wolfSSL Support
Hi muataz.m
Thanks for joining the wolfSSL Forums. Perhaps this will be useful:
https://learn.microsoft.com/en-us/xamar … tform/cpp/
If you're interested in having us create a Xamarin Forms port of wolfSSL, please send an email to
where we can create a feature request for you.
Thanks,
Eric - wolfSSL Support
Hi mrdebug,
Thanks for joining the wolfSSL Forums. Try enabling alternate cert chains with
./examples/client/client -h www.google.com -p 443 -g -v 3 -A google.crt
SSL version is TLSv1.2
SSL cipher suite is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
SSL curve name is SECP256R1
Alternate cert chain used
SSL connect ok, sending GET...
HTTP/1.0 200 OK
Date: Wed, 15 Mar 2023 13:34:58 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=ISO-8859-1
P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Server: gws
X-XSS-Protection: 0
X-Fra
Hi Shammon,
Thanks for joining the wolfSSL Forums. Please try including the wolfSSL config header before any other wolfSSL includes:
#ifndef WOLFSSL_USER_SETTINGS
#include <wolfssl/options.h>
#endif
#include <wolfssl/wolfcrypt/settings.h>
Thanks,
Eric - wolfSSL Support
It seems like we have the same conversation happening on two forums:
https://stackoverflow.com/questions/755 … to-sp-init
Let's just keep the conversation going here.
Thanks,
Eric - wolfSSL Support
Hi wangzihao,
Thanks for joining the wolfSSL Forums. Could you share the "./config" command you used?
Are you trying to use the math library directly in your application? If so you'll need to define "WOLFSSL_PUBLIC_MP" in the configuration. You should use the "mp_*" API instead of the direct "sp_*" functions.
Let us know if there are still questions.
Thanks,
Eric - wolfSSL Support
The RNG is required for resistance to timing attacks. If you are only doing this as research, you can disable the timing attack resistance by undefining
Hello kingutoran98,
We have an example that you might find useful:
https://github.com/wolfSSL/wolfssl-exam … ate_secret
Also this example is a good demonstration of using the x963 API:
https://github.com/wolfSSL/wolfssl-exam … glentest.c
What configuration settings are you building wolfSSL with?
Could you tell us about about your project?
Thanks,
Eric @ wolfSSL Support
Hi asigrijenny,
Welcome to the forums. The solution was posted here:
https://www.wolfssl.com/forums/post6393.html#p6393
Thanks,
Eric - wolfSSL Support
Hello Anika,
Yes, releases are always tagged as stable:
https://github.com/wolfSSL/wolfssl/rele … 5.4-stable
Thanks,
Eric - wolfSSL Support
Hi m_u_h
You could try simply setting the FIPS hash to an invalid value.
Hi Hodge,
Check out the project instructions from the readme:
https://github.com/wolfSSL/wolfssl/tree … om-scratch
In particular, confirm that the preprocessor macro "WOLFSSL_USER_SETTINGS" is set, per step 15
Thanks,
Eric
Hi Hodge,
Is "versal" defined? Otherwise it looks like "WOLFSSL_ARMASM" is being defined at the end:
#if !defined(WOLFSSL_XILINX_CRYPT_VERSAL)
/* Enable ARMv8 (Aarch64) assembly speedups - SHA256 / AESGCM */
/* Note: Requires CFLAGS="-mcpu=generic+crypto -mstrict-align" */
#define WOLFSSL_ARMASM
#endif
Hi senergy,
Thanks for joining the wolfSSL Forums. Using VS Code to build wolfSSL is pretty straightforward. Since you are trying to build for the RPi, you will need to have the right tools to cross compile. VS Code makes setting the target easy. Here is a tutorial that you might find useful:
https://enes-ozturk.medium.com/cross-co … ca4976fdd1
Since you also contacted our support email, we will follow up from there.
Thanks,
Eric - wolfSSL Support
Hello Hodge,
Thanks for joining the wolfSSL Forums. In your configuration, please ensure that either WOLFSSL_ARMASM or WOLFSSL_XILINX_CRYPT is defined, but not both.
Thanks,
Eric - wolfSSL Support
Posts found: 101 to 125 of 351
Generated in 0.021 seconds (76% PHP - 24% DB) with 4 queries