151 Reply by kareem_wolfssl

(11 replies, posted in wolfSSL)

Hi rahmanikivi724,

A couple of things to try.
First, you should always call wolfSSL_Init() before any other wolfSSL functions.
Second, try defining WOLFSSL_STM32F427_RNG to use our STM32F4xx codepath for your RNG.

If this doesn't help, please enable debugging by building with DEBUG_WOLFSSL and running wolfSSL_Debugging_ON() before your code, and attach debug logs.  The return code of wc_InitRng would also be helpful.

Thanks,
Kareem

Go to forum: wolfSSL

152 Reply by kareem_wolfssl

(3 replies, posted in wolfSSL)

Hello rahmanikivi724,

I would definitely recommend using our GCC-ARM example as you found, since it is set up for ARM platforms like yours.
Try defining NO_WOLFSSL_DIR to skip using DIR/dirent.h, and let me know if it helps.  You will want to include it in your CFLAGS, prefixed by -D.

Thanks,
Kareem

Go to forum: wolfSSL

153 Reply by kareem_wolfssl

(1 replies, posted in wolfSSL)

Hi stillwater,

We do not currently support custom handshake extensions.  I can enter a feature request for you, but there's no guarantee of when it will be implemented.
Alternatively, you can contact us at facts@wolfssl.com to discuss code consulting for this feature.

Thanks,
Kareem

Go to forum: wolfSSL

154 Reply by kareem_wolfssl

(3 replies, posted in wolfSSL)

Hello Mohannad,

Can you post your full configure line including LDFLAGS?  Does adding libgmp/pbc LDflags like this help?  LDFLAGS="-lpbc -lgmp ./configure ..."

Thanks,
Kareem

Go to forum: wolfSSL

155 Reply by kareem_wolfssl

(1 replies, posted in wolfMQTT)

Hi rlev,

Yes, when using the MqttClient_Subscribe API to subscribe, you can pass as many topics as you'd like in the array MqttSubscribe->topics as long as you set topic_count correctly.
Here are a couple of examples that subscribe to a single topic, to expand them you'd just iterate over each topic and set their parameters accordingly:
https://github.com/wolfSSL/wolfMQTT/blo … ent.c#L383
https://github.com/wolfSSL/wolfMQTT/blo … ple.c#L399

Thanks,
Kareem

Go to forum: wolfMQTT

156 Reply by kareem_wolfssl

(3 replies, posted in wolfSSH)

Hi rr9mvp,

Unfortunately no, our SCP implementation is part of wolfSSH just like our SFTP, and they're all on the same platforms which does not currently include FreeRTOS without a POSIX API.

Thanks,
Kareem

Go to forum: wolfSSH

157 Reply by kareem_wolfssl

(3 replies, posted in wolfSSH)

Hi rr9mvp,

While we have not ported wolfSSH/SFTP to FreeRTOS without POSIX, we have ported wolfSSH/SFTP to various platforms which you can find here:
https://github.com/wolfSSL/wolfssh/blob … ssh/port.h
https://github.com/wolfSSL/wolfssh/blob … src/port.c

If you are interested in having us help you port to your platform, please contact us at facts@wolfssl.com

Thanks,
Kareem

Go to forum: wolfSSH

158 Reply by kareem_wolfssl

(2 replies, posted in wolfSSL)

Hi rlev,

You should be able to silence these warnings using: 

-Wno-packed-not-aligned

I will look into getting these warnings fixed.

Thanks,
Kareem

Go to forum: wolfSSL

159 Reply by kareem_wolfssl

(2 replies, posted in cURL)

Hello Gary,

Do you see this issue with curl for all sites, or just microsoft.com?
Can you try the WOLFSSL_ALLOW_NO_CN_IN_SAN flag?
If that doesn't help, please generate a debug log by rebuilding with WOLFSSL_DEBUG defined and attach it here.  Please also include your curl command line or code.

For wolfSSL's client, try using -A to pass in your CA cert, not -a.

Thanks,
Kareem

Go to forum: cURL

160 Reply by kareem_wolfssl

(1 replies, posted in wolfSSL)

Hello Andreas,

If you are using mutual auth you could set up OCSP stapling in both directions, you will need to configure your OCSP responder for this.  wolfSSL will parse and verify OCSP responses, but it won't create the response itself.

Thanks,
Kareem

Go to forum: wolfSSL

161 Reply by kareem_wolfssl

(1 replies, posted in wolfSSL)

Hi Noufal,

See here for examples and documentation on building wolfSSL with Yocto: https://github.com/wolfSSL/meta-wolfssl

Thanks,
Kareem

Go to forum: wolfSSL

162 Reply by kareem_wolfssl

(4 replies, posted in wolfSSL)

I was able to reproduce your issue here.  It seems this server is not sending a correct record header, the record header has no version number so it is invalid.  Please confirm the server is set up correctly.

Thanks,
Kareem

Go to forum: wolfSSL

163 Reply by kareem_wolfssl

(2 replies, posted in wolfSSL)

Hello ENOTTY,

I was able to reproduce your issue on that commit.  Looks like we've just checked in a fix here:
https://github.com/wolfSSL/wolfssl/comm … 8a742dde57
I retested with this commit applied and everything is building for me now.  Let me know if it works for you.

Thanks,
Kareem

Go to forum: wolfSSL

164 Reply by kareem_wolfssl

(4 replies, posted in wolfSSL)

Hello yuliang136,

When you are receiving an error, what url are you passing to the -h option?

Thanks,
Kareem

Go to forum: wolfSSL

165 Reply by kareem_wolfssl

(1 replies, posted in wolfSSL)

Hello,

Before pursuing this approach, we do have various options which will reduce our code size.  Can you share your user_settings.h (or ./configure line), what platform you're on, what cipher suites/algorithms you need and what code size you need?

Feel free to email us at support@wolfssl.com for private support if any of this info is confidential.

Thanks,
Kareem

Go to forum: wolfSSL