aboutsummaryrefslogtreecommitdiff
path: root/ssh/tomsg_clientlib.c
Commit message (Collapse)AuthorAge
* ssh/tomsg_clientlib: Fix stuck-data bug in tomsg_next_eventTom Smeding2020-10-03
| | | | | | | | | | | 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.
* ssh: Update clientlib for protocol version 3Tom Smeding2020-10-03
|
* clientlib: Fix behaviour for zero historyTom Smeding2020-07-29
|
* clientlib: Support get_messageTom Smeding2020-07-29
|
* clientlib: Update to protocol version 2 with repliesTom Smeding2020-07-28
|
* ssh: Various connection closing fixesTom Smeding2020-07-27
|
* tomsg_clientlib: Let async event nullify take event by valueTom Smeding2020-07-13
|
* ssh: Less debug logging againTom Smeding2020-07-13
|
* tomsg_clientlib: Async connect routinesTom Smeding2020-07-13
| | | | | This is quite complex, and it probably can be implemented with a simpler API and implementation. Regardless, it _seems_ to work.
* tomsg_clientlib: Proper hostkey checkingTom Smeding2020-07-12
|
* tomsg_clientlib: Ensure tomsg_connect sets client to NULL on errorTom Smeding2020-07-12
|
* tomsg_clientlib: Elide redundant assignments in nullify()Tom Smeding2020-07-12
|
* Add tomsg client lib for CTom Smeding2020-07-12