mirror of https://github.com/wolfSSL/wolfssh.git
95369017da
ssh_worker() reads a WS_WANT_WRITE from wolfSSH_worker() as a send the socket has not taken yet: it waits for the socket to accept one and runs the worker again, rather than leaving the loop. Application-driven mode answers session requests here, and the peer waits on that reply, so a blocked one ended a session the legacy accept() carried through. - the worker runs on a writable socket as well as a readable one, or the owed send is never retried - the ssh socket joins the select write set only while a want-write is outstanding - a queued agent channel open joins the same wait, so the poll runs ahead of the write set |
||
|---|---|---|
| .. | ||
| client | ||
| echoserver | ||
| portfwd | ||
| scpclient | ||
| sftpclient | ||
| tpmcertserver | ||
| include.am | ||