Welcome to the wolfSSL Forums!

2022-02-21 06:09:35

Hello Olle,

In order to properly prioritize your request, please open a support ticket by emailing support@wolfssl.com

Thanks,
Eric @ wolfSSL Support

2022-02-17 08:16:23

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"

2022-02-16 06:25:04

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

2022-02-16 06:10:44

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

2022-02-14 14:49:46

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?

2022-01-31 15:02:03

@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.

2022-01-24 08:56:24

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.

2022-01-21 15:44:58

The parser is failing on the attribute

unstructuredName         :ovgu

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.

2022-01-21 13:59:02

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

2022-01-17 15:44:46

Hi Bruce,

Thanks for sending a message to support@wolfssl.com. We will assist you there.

2022-01-10 11:18:31

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"

2022-01-10 08:28:56

Hello Junkhar,

To better prioritize your support request, please open a ticket by sending an email to support@wolfssl.com

Thanks,
Eric @ wolfSSL Support

2022-01-10 07:54:01

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.

2022-01-07 15:51:22

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.

2021-12-20 14:29:27

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

2021-12-14 06:47:42

Your last message did not attach a pcap file

fail 2 test2.pcapng

2021-12-13 08:29:13

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

2021-12-09 18:04:46

Have you run the example stand-alone yet? It might be useful to see it working first, then try to integrate.

2021-12-09 09:32:16

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

2021-11-30 07:57:21

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/

2021-11-24 06:37:15

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

2021-11-09 14:39:28

Also, here is an example of a very minimal configuration for ECC. Perhaps it will be useful:
https://github.com/wolfSSL/wolfssl/blob … _min_ecc.h

2021-11-09 14:04:04

That does not sound outrageous.

Here is a guide you may find useful:
https://www.wolfssl.com/docs/wolfssl-ma … llocation/
In particular, the tuning section at the end.

2021-10-14 14:12:11

Hi Alex,

Nothing stands out as odd in the configuration. There could be an issue in how the application is handling the wolfSSL context.

Have you reviewed the examples repository? In particular this one may be of interest to you:
https://github.com/wolfSSL/wolfssl-exam … blocking.c

Thanks,
Eric @ wolfSSL Support

2021-10-13 08:08:13

Excellent. Right, if you had filled the buffer with data (used all 1024 bytes), then the sizeof operator would be correct.

Welcome to the wolfSSL Forums!

Search options (Page 9 of 15)

Posts found: 201 to 225 of 364

201 Reply by embhorn 2022-02-21 06:09:35

Re: Need support for userid in Subject name of CSR (1 replies, posted in wolfSSL)

202 Reply by embhorn 2022-02-17 08:16:23

Re: Cannot crosscompil wolfssl 5.1.1 (7 replies, posted in wolfSSL)

203 Reply by embhorn 2022-02-16 06:25:04

Re: Intel hex format (2 replies, posted in wolfBoot)

204 Reply by embhorn 2022-02-16 06:10:44

Re: Intel hex format (2 replies, posted in wolfBoot)

205 Reply by embhorn 2022-02-14 14:49:46

Re: Cannot crosscompil wolfssl 5.1.1 (7 replies, posted in wolfSSL)

206 Reply by embhorn 2022-01-31 15:02:03

Re: Generate certificate from certificate request (6 replies, posted in wolfCrypt)

207 Reply by embhorn 2022-01-24 08:56:24

Re: ParseCert returns -144. on RIOT Os (6 replies, posted in wolfCrypt)

208 Reply by embhorn 2022-01-21 15:44:58

Re: ParseCert returns -144. on RIOT Os (6 replies, posted in wolfCrypt)

209 Reply by embhorn 2022-01-21 13:59:02

Re: ParseCert returns -144. on RIOT Os (6 replies, posted in wolfCrypt)

210 Reply by embhorn 2022-01-17 15:44:46

Re: Using Wolfssl and WolfMQTT with Arduino (1 replies, posted in wolfSSL)

211 Reply by embhorn 2022-01-10 11:18:31

Re: Building wolfcrypt with clang 13 for a cross ARM/thumb target (5 replies, posted in wolfCrypt)

212 Reply by embhorn 2022-01-10 08:28:56

Re: PIC32/FreeRTOS handshake failure TLS 1.3 (11 replies, posted in wolfSSL)

213 Reply by embhorn 2022-01-10 07:54:01

Re: Building wolfcrypt with clang 13 for a cross ARM/thumb target (5 replies, posted in wolfCrypt)

214 Reply by embhorn 2022-01-07 15:51:22

Re: WolfSSL on RIoT OS (2 replies, posted in wolfSSL)

215 Reply by embhorn 2021-12-20 14:29:27

Re: SSL_connect fail (8 replies, posted in wolfSSL)

216 Reply by embhorn 2021-12-14 06:47:42

Re: SSL_connect fail (8 replies, posted in wolfSSL)

217 Reply by embhorn 2021-12-13 08:29:13

Re: SSL_connect fail (8 replies, posted in wolfSSL)

218 Reply by embhorn 2021-12-09 18:04:46

Re: PIC32/FreeRTOS handshake failure TLS 1.3 (11 replies, posted in wolfSSL)

219 Reply by embhorn 2021-12-09 09:32:16

Re: PIC32/FreeRTOS handshake failure TLS 1.3 (11 replies, posted in wolfSSL)

220 Reply by embhorn 2021-11-30 07:57:21

Re: WolfMQTT on NXP T2080 and VxWork 7 and PykoOS and LX2020 (7 replies, posted in wolfMQTT)

221 Reply by embhorn 2021-11-24 06:37:15

Re: ARP Protocol in wolfssl (1 replies, posted in wolfSSL)

222 Reply by embhorn 2021-11-09 14:39:28

Re: Wolfcrypt minimum RAM footprint for RSA2048 or ECC384 (3 replies, posted in wolfCrypt)

223 Reply by embhorn 2021-11-09 14:04:04

Re: Wolfcrypt minimum RAM footprint for RSA2048 or ECC384 (3 replies, posted in wolfCrypt)

224 Reply by embhorn 2021-10-14 14:12:11

Re: Server on embedded device (16 replies, posted in wolfSSL)

225 Reply by embhorn 2021-10-13 08:08:13

Re: Diffrent digest in compare of Online hash fucntion (5 replies, posted in wolfSSL)

Posts found: 201 to 225 of 364