Lakshya Chopra

Hello, Thank you for your response. Sorry, for not being able to provide an example, but I would like to provide a brief context regarding our usage of (PQ) DTLS...

Hello @rizlik , Thank you for your response! I will try out this method and will follow up soon with the results. Appreciate your help.

Unfortunately, I couldn't get this method to work too.  Thanks for your time & efforts.

Hello @rizlik , To be precise that segmentation fault isn't really associated with the wolfSSL code, it was due to a logical bug where I tried to access the wolfSSL...

In this case, CU (`TASK_CU`) is the server, and DU (`TASK_DU`) is the client.

Well yes. I believe that this could be done, we'll consider your suggestion, and will try to implement it if feasible. Thanks!

Update: Sorry for the late response, I have just resumed that project after a month. It seems that the SCTP Task is already split into 2 different contexts, one for...

Sure, I can shift to a private mail conversation. However, I would like to provide some debug logs that I got after turning the debugging on: ```bash wolfSSL Entering wolfSSL_SSL_do_handshake...

Hello @rizlik Here is the wolfSSL configuration I am using: `./configure --with-liboqs --enable-experimental --enable-dtls13 --enable-dtlscid --enable-dtls-frag-ch --enable-tls13 --enable-dtls --enable-sctp --enable-opensslextra --enable-opensslall ` Also, thank you for the insight. Edit: I...

After changing the wolfSSL config, I retested the app and this time I'm getting these errors: Client:  Server: