1 Topic by Nitay (edited by Nitay 2013-06-13 06:33:35)

  • Registered: 2013-05-22
  • Posts: 11

Topic: Using wolfSSL embedded SSL with an asynchronous socket

Hello,

I have tcp server which uses multiple threads for reading through an IO Completion Port. I want to add SSL to this server.

What, in your opinion, is the best way to do so?
The writes are less of a problem, but how do I decrypt a SSL packet without calling read?

For now, I've set the write and read callbacks using wolfSSL_SetIORecv / wolfSSL_SetIOSend.
I didn't implement the reads yet.
Also, the accept could be done to a new client before attaching it to the IOCP, so its not really a non-blocking IO...

What do you think?

EDIT: The reads are done through IOCP, so the threads are not blocked on recv() or select(), but on GetQueuedCompletionStatus()

Thanks
Nitay

Share

  • From: Bozeman, MT
  • Registered: 2010-10-20
  • Posts: 647

Re: Using wolfSSL embedded SSL with an asynchronous socket

Hi Nitay,

Section 9.4 of the wolfSSL Manual (http://www.yassl.com/yaSSL/Docs-cyassl- … esign.html) talks a little about wolfSSL's thread safety.  Have you looked through that?

wolfSSL is generally thread safe, but reading from or writing to the same WOLFSSL object with multiple threads at one time is not supported.  You'll need to protect calls to wolfSSL_read() and wolfSSL_write() on the same WOLFSSL object with a mutex or similar to avoid more than one thread trying to call it simultaneously.

Best Regards,
Chris

https://www.wolfssl.com

chrisc's Website

Share

3 Reply by Nitay (edited by Nitay 2013-06-13 08:56:30)

  • Registered: 2013-05-22
  • Posts: 11

Re: Using wolfSSL embedded SSL with an asynchronous socket

Hi,

I'm less concerned about thread safety since I can limit thread access per session. I'm just not sure about how can I use wolfSSL if my reads are done outside the library, and not through the SSL_Read function

Thanks
Nitay

Share

  • From: Bozeman, MT
  • Registered: 2010-10-20
  • Posts: 647

Re: Using wolfSSL embedded SSL with an asynchronous socket

Nitay,

It sounds like you're on the right track with registering your own I/O callbacks.  The callbacks were designed to allow applications to control how they read/write data to/from wolfSSL.  For your Recv callback, you'll just need to pass the encrypted data buffer received over your transport medium to wolfSSL through the provided buffer, "buf", in your callback.  For an example, you can reference the EmbedReceive() function in <wolfssl_root>/src/io.c.

I'm not familiar with IOCP myself, so if I'm misunderstanding what you are trying to do, please correct me.

Best Regards,
Chris

https://www.wolfssl.com

chrisc's Website

Share

  • Registered: 2013-05-22
  • Posts: 11

Re: Using wolfSSL embedded SSL with an asynchronous socket

Hello,

The problem is - The callback is only being called if the SSL_Read function is called. The threads that are reading are receiving messages asynchronously, meaning I don't know when a message will be received...

One way I can think of is inserting the newly received message into a queue, and then calling to SSL_Read explicitly, overriding the read callback to get the message from the queue.
But that seems kind of crooked (And needs to be well designed thread-safety-wise)

The higher levels (i.e. the Business Logic that uses the TCP server) are built based on asynchronous messaging as well, so I'd like to keep the reading method as it is

Thanks
Nitay

Share

  • Registered: 2014-05-18
  • Posts: 1

Re: Using wolfSSL embedded SSL with an asynchronous socket

I'm in a similar situation as the OP. Has this ever been resolved?

Thanks

Share

  • Registered: 2020-04-01
  • Posts: 1

Re: Using wolfSSL embedded SSL with an asynchronous socket

I know this is an old thread but could you please clarify this response:

"You'll need to protect calls to wolfSSL_read() and wolfSSL_write() on the same WOLFSSL object with a mutex or similar to avoid more than one thread trying to call it simultaneously."

Does that mean that I just need to protect against multiple calls to wolfSSL_read() and multiple calls to wolfSSL_write() and so can have a separate mutex for each or do I also need to prevent a call to wolfSSL_write() while another thread is in wolfSSL_read() and vice-versa?

I hope not or this would mean it is impossible to use a blocking receive interface at the socket transport layer in a multi-threaded environment, as while the receive is waiting for data, no-one would be able to send anything.

Kind Regards,
Simon Raybould,
Firmware Developer, Landis+Gyr, Switzerland.

Share

  • From: Bozeman
  • Registered: 2014-05-09
  • Posts: 776

Re: Using wolfSSL embedded SSL with an asynchronous socket

Does that mean that I just need to protect against multiple calls to wolfSSL_read() and multiple calls to wolfSSL_write() and so can have a separate mutex for each or do I also need to prevent a call to wolfSSL_write() while another thread is in wolfSSL_read() and vice-versa?

To better clarify wolfSSL, for embedded design reasons, uses a single I/O buffer since TLS packets can be up to 16k we thought it unreasonable for resource constrained devices to have to maintain 32k for thread safe reads and writes, the overhead was too much. Because there is only one buffer used for both sending and receiving send calls can corrupt data that is not yet read. Similarly read calls can corrupt data that is not yet sent. A single mutex should be used to protect against both wolfSSL_read and wolfSSL_write calls on the same SSL object.

For blocking setups we added a feature called "write duplicate". This is where you use one SSL object to connect to a server. Once the connection is established and the handshake is complete you can make a duplicate of the SSL object for writing only. Then the first SSL object becomes a read only object. This gives a solution for the scenario SieRaybould noted but also adds that overhead of 32k for thread safe reading and writing. See wolfSSL_write_dup(ssl); for creating a write duplicate of an SSL object.



Warm Regards,

K

Kaleb J. Himes's Website

Share