176 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

177 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

178 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

179 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

180 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

181 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

182 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

183 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

184 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

185 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