ssh/tomsg_clientlib: Fix stuck-data bug in tomsg_next_event

The issue was that I have too many buffering layers. The bug occurred
when the sshnc layer had received some amount of data, some of which
(but not all of which) was passed on to tomsg_clientlib via
sshnc_maybe_recv in receive_more_data. If the data that _was_ passed on
did not constitute a full event, tomsg_clientlib did not ask for more
data from the sshnc layer; it would only get received the next time
there was actual data on the _socket_, at which point poll(2) would
ensure the whole chain gets looped through another time.

0 files changed, 0 insertions, 0 deletions