Quote:
Originally Posted by NiLuJe
Here goes. Completely untested, because I'm lazy  .
For a K4 & PW1, use the binary in the K5 folder. |
Ah, phooey, 1am and nothing else to read . . . .
So I read the source code (for the first time).
The application attempts to be non-blocking while servicing multiple connections.
Only (Open)SSL is used in blocking mode
AND
(Open)SSL is not coded to handle multiple connections in blocking mode (I.E: the single SSL_CTX is not "multiple use").
The (Open)SSL parts of the code should be written using non-blocking mode (and with the appropriate tests and callbacks).
https://www.openssl.org/support/faq.html#PROG10
Translation:
Application can handle multiple channels, on multiple servers, but only one of them can be SSL.
Making more than a single SSL connection at once will lead to strange and wonderful connection errors.
I don't **think** it will segfault, but the connections will be garbage.
Edit: (after seven hours of sleep) - -
Don't anyone panic, this is known to work on the Kindles.
Meanwhile, I will re-read this source code while mind is closer to being "in gear" rather than dreaming.