Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | ssh/tomsg_clientlib: Fix stuck-data bug in tomsg_next_event | Tom Smeding | 2020-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 3 | Tom Smeding | 2020-10-03 |
| | |||
* | clientlib: Fix behaviour for zero history | Tom Smeding | 2020-07-29 |
| | |||
* | clientlib: Support get_message | Tom Smeding | 2020-07-29 |
| | |||
* | clientlib: Update to protocol version 2 with replies | Tom Smeding | 2020-07-28 |
| | |||
* | ssh: Various connection closing fixes | Tom Smeding | 2020-07-27 |
| | |||
* | tomsg_clientlib: Let async event nullify take event by value | Tom Smeding | 2020-07-13 |
| | |||
* | ssh: Less debug logging again | Tom Smeding | 2020-07-13 |
| | |||
* | tomsg_clientlib: Async connect routines | Tom Smeding | 2020-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 checking | Tom Smeding | 2020-07-12 |
| | |||
* | tomsg_clientlib: Ensure tomsg_connect sets client to NULL on error | Tom Smeding | 2020-07-12 |
| | |||
* | tomsg_clientlib: Elide redundant assignments in nullify() | Tom Smeding | 2020-07-12 |
| | |||
* | Add tomsg client lib for C | Tom Smeding | 2020-07-12 |