Hello mrinalilothey

Welcome to the wolfSSL Forums.

We have some example projects for IAR Workbench to get you started:
https://github.com/wolfSSL/wolfssl/tree … /IAR-EWARM

Let us know if there are questions. You can always open a support ticket by emailing support@wolfssl.com

Could you tell us a bit about your project using wolfSSL?

Thanks,
Eric - wolfSSL Support

Hi invoker,

I would recommend opening a support ticket by emailing support@wolfssl.com

Thanks,
Eric

Could you create a test case using the wolfSSL examples?

<wolfssl>./examples/server/server

<wolfssl>./examples/client/client

Hello forza,

Thanks for joining the wolfSSL Forums. wolfSSH-sshd is intended to be full replacement for the OpenSSH server. Here is a getting started video:
https://www.youtube.com/watch?v=xJOyoalxA0U

This is relatively new feature of the project, so documentation is still forthcoming.

I'll check with the team about the key-gen tool.

Could you tell us a bit about your project using wolfSSH? Feel free to email us at support@wolfssl.com for a more private discussion.

Kind regards,
Eric - wolfSSL Support

Hello invoker,

Thanks for joining the wolfSSL Forums. Unfortunately we needed to disable file attachments in these forums, so I am unable to see your log.

You are welcome to create a support ticket by emailing support@wolfssl.com

Are you connecting to one of the wolfSSL example servers?

Kind regards,
Eric - wolfSSL Support

Hello medyuuna,

Thanks for joining the wolfSSL Forums. I was able to reproduce the issue you reported. I have created a fix in the PR:
https://github.com/wolfSSL/wolfssh/pull/716

Please test it and let me know if this resolves the issue for you also.

Could you tell us a bit about your project using wolfSSH? Feel free to email us at support@wolfssl.com for a more private conversation.

Kind regards,
Eric - wolfSSL Support

I really should have mentioned this before, but you should review the sniffer code:
https://github.com/wolfSSL/wolfssl/tree … sslSniffer

Specifically the code around checking for application data:
https://github.com/wolfSSL/wolfssl/blob … er.c#L6413

Yes, v3.15.7 supports ECC-P256 by default.
https://github.com/wolfSSL/wolfssl/blob … #L188-L189

The wolfSSL IO layer is only requesting reads from the driver layer. So first it requests 5 bytes (the TLS header) which contains the packet size. Then we ask for the full remainder of the TLS packet, however they can return less. The read callback will continue to be called until the full TLS header has been read. Then it will ask for 5 bytes again. If you return more than asked it would be an error.

Hello mabduljawad

Thanks for joining the wolfSSL forums! The wolfMQTT library will only use malloc if configured to allocate MQTTv5 properties dynamically. By default, the library is stack-only.

For wolfSSL, check out the static memory guide:
https://www.wolfssl.com/docs/static-buffer-allocation/

Could you tell us a bit about your MQTT project? Feel free to email support@wolfssl.com for a more private discussion.

Thanks,
Eric - wolfSSL Support

Hello east1ifep

Thanks for your question. We had to disable attachments in the forums, so I cannot review your pcap and log.

Could you please send this request to support@wolfssl.com, and we'll get a proper support ticket created to help you out.

Kind regards,
Eric - wolfSSL Support

Hi horroraround,

Thanks for joining the wolfSSL Forums. The max props define is set to 30, and can be overridden by defining MQTT_MAX_PROPS at build time. This was a design decision that allowed us to keep the library requirements small and still allow flexibility for applications.

Alternatively, if your application can tolerate dynamic memory usage, the library can allocate property structures dynamically using malloc. Just add the configuration define WOLFMQTT_DYN_PROP to enable this feature.

Thanks,
Eric - wolfSSL Support