On 11.02.19 09:04, g4-l...@tonarchiv.ch wrote:
> Hi there
>
> Could someone reproduce this? You need something else to accept the patch?
>
Ignore this mail... I should check Git more often :-))
On 30.01.19 15:33, g4-l...@tonarchiv.ch wrote:
> Hi all,
>
> You finally find the test code attached. It's a bit complicated, but
> it can reproduce the issue:
>
> 1. Connect to an ssh server which supports direct socket tunnelling:
>
> > ./multichannelfw root myserver.com 22
>
> This opens a loca
Hi Andreas,
did you test it? It would be great if this patch could go to the lib. At
the moment I have to statically link my ssh app with my own libssh
version...
Cheers,
Till
On 30.01.19 15:33, g4-l...@tonarchiv.ch wrote:
>
> Hi all,
>
> You finally find the test code attached. It's a bit compl
Hi all,
You finally find the test code attached. It's a bit complicated, but it
can reproduce the issue:
1. Connect to an ssh server which supports direct socket tunnelling:
> ./multichannelfw root myserver.com 22
This opens a local listening port at 20021
2. Open two or more simultaneous ssh
On Tuesday, 29 January 2019 12:05:28 CET g4-l...@tonarchiv.ch wrote:
> On 29.01.19 09:49, Andreas Schneider wrote:
> > On Monday, 28 January 2019 23:10:09 CET g4-l...@tonarchiv.ch wrote:
> >> Hi all
> >>
> >> There's a bug in the connector API when subsequently adding to and
> >> removing connecto
On 29.01.19 09:49, Andreas Schneider wrote:
> On Monday, 28 January 2019 23:10:09 CET g4-l...@tonarchiv.ch wrote:
>> Hi all
>>
>> There's a bug in the connector API when subsequently adding to and
>> removing connectors from an event loop.
>>
>> Here's some dummy code to reproduce it (I will add r
Hi all
There's a bug in the connector API when subsequently adding to and
removing connectors from an event loop.
Here's some dummy code to reproduce it (I will add real code later):
event = ssh_event_new();
/* ADD FIRST connector pair (in/out) */
ssh_connector in1 = ssh_connector_new(session);
