SecureConnection crashes if receiving too many messages at once
Created by: agraubert
From a preliminary check, it looks to be an issue with QueuedSocket, but I can't be sure yet. I'll update the title if that becomes the case.
The basic error is that the underlying SecureSocket receives some data out of order. It expects to receive the hex-encoded chunk count for an AES encrypted command, but instead gets what appears to be the command payload. This may also be a race condition for which text_out thread on the sender's side pumps data through the command pipe first. If that's the case then the cmd channel should be reserved entirely for single payload command strings