151

(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

152

(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

153

(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

154

(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

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

156

(4 replies, posted in wolfSSL)

Hello yuliang136,

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

Thanks,
Kareem

157

(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