I want to pass a [`tls.CleartextStream`](http://nodejs.org/api/tls.html#tls_class_tls_cleartextstream) instance to a worker process (created by [cluster.fork()](http://nodejs.org/api/cluster.html#cluster_cluster_fork_env) method). While I can send `net.Socket` instances using the [send(message, handle)](http://nodejs.org/api/child_process.html#child_process_child_send_message_sendhandle) method I can't do the same using the ClearStream class. 

Might there be a way to "rewrap" the connected raw socket by serializing the original CleartextStream instance?

This is what I want to achieve: The master process of a Node.js application is listening for TLS connections. There are a number of certain worker processes which where spawned at startup. A client connected to the master process want to be redirected to *a certain* worker process. Therefore the master should send the socket to the corresponding worker process. This actually works but as the TLS context gets lost the worker process can neither de- nor encode data to communicate to the connected client.

![enter image description here](https://i.stack.imgur.com/QSPUw.png)

Do you have any idea how this could be realized?