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 6 of 12)
Pages Previous 1 … 4 5 6 7 8 … 12 Next
A new source file was added,
/wolfssl/wolfcrypt/src/kdf.c
, and it is not being built by your VS project.
The VS project files in the repository have been updated in the latest release.
This is an informative error and it indicates that the peer has closed the connection and no more data will be expected.
I would suggest opening a support ticket by emailing support@wolfssl.com
MCPU is supported by arm-linux-gcc
https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html
-mcpu=name[+extension…]
This specifies the name of the target ARM processor. GCC uses this name to derive the name of the target ARM architecture (as if specified by -march) and the ARM processor type for which to tune for performance (as if specified by -mtune). Where this option is used in conjunction with -march or -mtune, those options take precedence over the appropriate part of this option.
Hello rlev,
With wolfMQTT, you can change the broker IP during the network connect using
. If the client was already connected to a different broker, you would need to first need to disconnect (
)
Hello Olle,
In order to properly prioritize your request, please open a support ticket by emailing support@wolfssl.com
Thanks,
Eric @ wolfSSL Support
Please try adding a CPU in the CFLAGS:
GENERIC EXAMPLE:
./configure \
CC="/path/to/your/toolchain/toolchain-gcc" \
AR="/path/to/your/toolchain/toolchain-ar" \
AS="/path/to/your/toolchain/toolchain-gcc" \
RANLIB="/path/to/your/toolchain/toolchain-ranlib" \
LD="/path/to/your/toolchain/toolchain-ld" \
--host=<your host> \
<your other configure options here> \
CFLAGS="-mcpu=<your cpu definition here> \
<other cflags here>" \
LIBS="<libs>"
SPECIFIC EXAMPLE:
./configure \
CC="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc" \
AR="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ar" \
AS="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc" \
RANLIB="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ranlib" \
LD="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ld" \
--host=arm-none-eabi \
--enable-aesgcm --enable-ecc \
CFLAGS="-mcpu=cortex-m4 \
-Os -specs=rdimon.specs" \
LIBS="-Wl,--start-group -lm -lgcc -lc -lrdimon -Wl,--end-group"
Hi Galadrius,
wolfBoot does not support the Intel HEX format directly, but it can be easily converted to bin via objcopy:
e.g. on arm-cortex:
arm-none-eabi-objcopy --input-target=ihex --output-target=binary firmware_v1.hex firmware_v1.bin
Hi Galadrius,
I've moved this discussion to the wolfBoot sub-forum, as you were referencing the wolfBoot documentation:
https://github.com/wolfSSL/wolfBoot/blo … Signing.md
I'll check with the team to see what image formats are supported by wolfBoot.
Thanks,
Eric
Hi alen.loncaric
Thanks for contacting wolfSSL. Typically this is because the settings are not getting picked up by the configuration headers. Could you please share the "./configure" command you are using?
@adarshr.r6 and @SheilaLyons
We have some excellent CSR examples here:
https://github.com/wolfSSL/wolfssl-exam … er/certgen
If you still have questions, please feel free to email support@wolfssl.com to open a ticket.
Thanks for clarifying. I was able to reproduce a similar error
Creating certificate...
Failure code was -134
...with
./configure --enable-certgen --enable-certext --enable-certreq --enable-keygen --enable-debug
But with
./configure --enable-all --enable-debug
the example works correctly. I will work on updating the example instructions.
The parser is failing on the attribute
openssl req -in testcsr2.pem -noout -text
Certificate Request:
Data:
Version: 1 (0x0)
Subject: C = DE, ST = BW, L = KER, O = OVGU, OU = COMSYS, CN = testName, emailAddress = xyz@ovgu.de
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
Public-Key: (256 bit)
pub:
04:6b:61:17:b7:64:a7:c8:64:ef:7e:1b:df:81:d7:
3b:68:cf:d5:77:f3:26:6a:5a:7e:81:cd:b0:02:25:
b4:7f:ff:42:62:44:dd:e3:e0:40:49:89:8d:ff:d7:
e5:36:3b:b0:cb:d1:1b:2d:59:89:de:3e:6e:12:46:
2a:56:a2:37:5a
ASN1 OID: prime256v1
NIST CURVE: P-256
Attributes:
unstructuredName :ovgu
challengePassword :1234
Signature Algorithm: ecdsa-with-SHA256
30:45:02:21:00:d3:cf:8a:a5:95:9f:fa:cb:84:dd:bf:ed:a8:
7b:4a:91:ba:a2:6f:ef:cf:19:41:40:c2:ab:d8:db:b3:95:c9:
53:02:20:3b:4c:fb:75:08:12:09:93:e3:66:7a:9f:35:12:4c:
de:ca:1d:24:f0:eb:40:8d:a0:66:28:71:9f:5e:54:1a:40
Here is some relevant information:
https://stackoverflow.com/questions/187 … cturedname
Try rebuilding the CSR without entering the unstructuredName field.
Hi adarshr.r6
Thanks for contacting wolfSSL. Typically we would like to review the problematic CSR. If you'd rather not share on this public forum, you are welcome to submit a support request by emailing support@wolfssl.com
Hi Bruce,
Thanks for sending a message to support@wolfssl.com. We will assist you there.
GENERIC EXAMPLE:
./configure \
CC="/path/to/your/toolchain/toolchain-gcc" \
AR="/path/to/your/toolchain/toolchain-ar" \
AS="/path/to/your/toolchain/toolchain-gcc" \
RANLIB="/path/to/your/toolchain/toolchain-ranlib" \
LD="/path/to/your/toolchain/toolchain-ld" \
--host=<your host> \
--target=<your target> \
<your other configure options here> \
CFLAGS="-mcpu=<your cpu definition here> \
<other cflags here>" \
LIBS="<libs>"
SPECIFIC EXAMPLE:
./configure \
CC="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc" \
AR="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ar" \
AS="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc" \
RANLIB="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ranlib" \
LD="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ld" \
--host=arm-none-eabi \
--enable-aesgcm --enable-ecc \
CFLAGS="-mcpu=cortex-m4 \
-Os -specs=rdimon.specs" \
LIBS="-Wl,--start-group -lm -lgcc -lc -lrdimon -Wl,--end-group"
Hello Junkhar,
To better prioritize your support request, please open a ticket by sending an email to support@wolfssl.com
Thanks,
Eric @ wolfSSL Support
Hello Rod,
Please review the section on cross compiling in the wolfSSL User Manual:
https://www.wolfssl.com/docs/wolfssl-ma … users%20on
Let us know if there are questions.
Hi adarshr.r6
Thank you so much for reaching out to wolfSSL support, can you tell us a bit about what you are working on and the high-level overview of the project to help us better classify this inquiry? Thank you in advance!
Your application must include the wolfSSL configuration headers before any others.
https://github.com/wolfSSL/wolfssl-exam … -tls.c#L34
/* wolfSSL */
#include <wolfssl/options.h>
#include <wolfssl/ssl.h>
Let us know if there are questions.
Please try only creating a new SSL object, instead of a new CTX and SSL. Here is an example:
https://github.com/wolfSSL/wolfssl-exam … tls-perf.c
Your last message did not attach a pcap file
Could you share the wolfSSL configuration? Also a log and pcap is very useful in determining why a connection is failing. If you'd prefer to keep this information private, please feel free to open a support ticket by emailing support @ wolfssl.com
Have you run the example stand-alone yet? It might be useful to see it working first, then try to integrate.
Hello Junkhar,
Thanks for contacting wolfSSL Support. Which Harmony webserver example project are you testing with?
Browsers often open multiple TLS connections to help speed up displaying a webpage. This can cause issues with embedded servers. Are you seeing a single connection succeed? If you test with wget does it work?
Thanks,
Eric
Hello Davide,
You'll want to cross-compile the library. Here is an example:
GENERIC EXAMPLE:
./configure \
CC="/path/to/your/toolchain/toolchain-gcc" \
AR="/path/to/your/toolchain/toolchain-ar" \
AS="/path/to/your/toolchain/toolchain-gcc" \
RANLIB="/path/to/your/toolchain/toolchain-ranlib" \
LD="/path/to/your/toolchain/toolchain-ld" \
--host=<your host> \
<your other configure options here> \
CFLAGS="-mcpu=<your cpu definition here> \
<other cflags here>" \
LIBS="<libs>"
SPECIFIC EXAMPLE:
./configure \
CC="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc" \
AR="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ar" \
AS="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc" \
RANLIB="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ranlib" \
LD="/usr/local/gcc_arm/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-ld" \
--host=arm-none-eabi \
--enable-aesgcm --enable-ecc \
CFLAGS="-mcpu=cortex-m4 \
-Os -specs=rdimon.specs" \
LIBS="-Wl,--start-group -lm -lgcc -lc -lrdimon -Wl,--end-group"
Chapter 2.6 of the wolfSSL manual will be helpful, as the same rules apply to wolfMQTT.
https://www.wolfssl.com/docs/wolfssl-manual/ch2/
Hello Akhi,
The wolfSSL interface is agnostic to the underlying transport layer. As such, it does not provide a method for fetching the MAC address. TI-RTOS does provide such capability:
https://www.ti.com/tool/NDKTCPIP
Kind regards,
Eric @ wolfSSL Support
Posts found: 126 to 150 of 293
Pages Previous 1 … 4 5 6 7 8 … 12 Next
Generated in 0.021 seconds (81% PHP - 19% DB) with 5 queries