Hi,
who knows which version of libssh we are using with current Windows client? Last week I was on site of one of my customers and investigated the issue when X2Go Client on Windows 10 was not able to open SSH channel with libssh error "socket error: No error". Apparently customer has this problem sometimes, not very often. But in case, when customer opened a session over SSH proxy, he was able to reproduce the issue in every 3rd-4th connection. I tried to build several versions of libssh for testing. With 0.7.7 I was still able to reproduce such behavior. After that I built the most recent version (0.9.2). We're still testing it, but looks like we don't have this issue any more. So, I was thinking maybe we should update libssh library in our Windows client.
regards, Alex
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
On Thu, Nov 7, 2019 at 12:24 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Hi,
who knows which version of libssh we are using with current Windows client? Last week I was on site of one of my customers and investigated the issue when X2Go Client on Windows 10 was not able to open SSH channel with libssh error "socket error: No error". Apparently customer has this problem sometimes, not very often. But in case, when customer opened a session over SSH proxy, he was able to reproduce the issue in every 3rd-4th connection. I tried to build several versions of libssh for testing. With 0.7.7 I was still able to reproduce such behavior. After that I built the most recent version (0.9.2). We're still testing it, but looks like we don't have this issue any more. So, I was thinking maybe we should update libssh library in our Windows client.
Still 0.7.4: https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=copy-deps-win32.bat https://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=tree;f=libssh
We still have to patch each version to use pageant (see the folder above). It has always been feasible to forward-port the patch to new minor releases (and micro releases.) However, upstream wants a more generic change in order to merge it: https://bugs.libssh.org/T27
-Mike
Ok, I see. We don't need to rush, but we should think about upgrade of libssh one time. I think it's quite important to get rid of this annoying issue, when the X2Go Client crashes because of some bug in the libssh. I'll see the customer in 3 weeks again and will let you know how tests are going. Than we can talk about it again.
regards Alex
Am 07.11.19 um 12:16 schrieb Mike DePaulo:
On Thu, Nov 7, 2019 at 12:24 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Hi,
who knows which version of libssh we are using with current Windows client? Last week I was on site of one of my customers and investigated the issue when X2Go Client on Windows 10 was not able to open SSH channel with libssh error "socket error: No error". Apparently customer has this problem sometimes, not very often. But in case, when customer opened a session over SSH proxy, he was able to reproduce the issue in every 3rd-4th connection. I tried to build several versions of libssh for testing. With 0.7.7 I was still able to reproduce such behavior. After that I built the most recent version (0.9.2). We're still testing it, but looks like we don't have this issue any more. So, I was thinking maybe we should update libssh library in our Windows client.
Still 0.7.4: https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=copy-deps-win32.bat https://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=tree;f=libssh
We still have to patch each version to use pageant (see the folder above). It has always been feasible to forward-port the patch to new minor releases (and micro releases.) However, upstream wants a more generic change in order to merge it: https://bugs.libssh.org/T27
-Mike
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
If you already built 0.9.2 and have a build environment ready to go, would you be able to forward-port the patch, and share the patch / binaries with via the 2nd git repo I linked to?
On Thu, Nov 7, 2019 at 1:26 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Ok, I see. We don't need to rush, but we should think about upgrade of libssh one time. I think it's quite important to get rid of this annoying issue, when the X2Go Client crashes because of some bug in the libssh. I'll see the customer in 3 weeks again and will let you know how tests are going. Than we can talk about it again.
regards Alex
Am 07.11.19 um 12:16 schrieb Mike DePaulo:
On Thu, Nov 7, 2019 at 12:24 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Hi,
who knows which version of libssh we are using with current Windows client? Last week I was on site of one of my customers and investigated the issue when X2Go Client on Windows 10 was not able to open SSH channel with libssh error "socket error: No error". Apparently customer has this problem sometimes, not very often. But in case, when customer opened a session over SSH proxy, he was able to reproduce the issue in every 3rd-4th connection. I tried to build several versions of libssh for testing. With 0.7.7 I was still able to reproduce such behavior. After that I built the most recent version (0.9.2). We're still testing it, but looks like we don't have this issue any more. So, I was thinking maybe we should update libssh library in our Windows client.
Still 0.7.4: https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=copy-deps-win32.bat https://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=tree;f=libssh
We still have to patch each version to use pageant (see the folder above). It has always been feasible to forward-port the patch to new minor releases (and micro releases.) However, upstream wants a more generic change in order to merge it: https://bugs.libssh.org/T27
-Mike
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
Yes, but I don't have access to it now. I'll do it in 2 weeks. Till that moment we'll see how X2Go Client works with the library I built.
Am 07.11.19 um 17:16 schrieb Mike DePaulo:
If you already built 0.9.2 and have a build environment ready to go, would you be able to forward-port the patch, and share the patch / binaries with via the 2nd git repo I linked to?
On Thu, Nov 7, 2019 at 1:26 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Ok, I see. We don't need to rush, but we should think about upgrade of libssh one time. I think it's quite important to get rid of this annoying issue, when the X2Go Client crashes because of some bug in the libssh. I'll see the customer in 3 weeks again and will let you know how tests are going. Than we can talk about it again.
regards Alex
Am 07.11.19 um 12:16 schrieb Mike DePaulo:
On Thu, Nov 7, 2019 at 12:24 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Hi,
who knows which version of libssh we are using with current Windows client? Last week I was on site of one of my customers and investigated the issue when X2Go Client on Windows 10 was not able to open SSH channel with libssh error "socket error: No error". Apparently customer has this problem sometimes, not very often. But in case, when customer opened a session over SSH proxy, he was able to reproduce the issue in every 3rd-4th connection. I tried to build several versions of libssh for testing. With 0.7.7 I was still able to reproduce such behavior. After that I built the most recent version (0.9.2). We're still testing it, but looks like we don't have this issue any more. So, I was thinking maybe we should update libssh library in our Windows client.
Still 0.7.4: https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=copy-deps-win32.bat https://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=tree;f=libssh
We still have to patch each version to use pageant (see the folder above). It has always been feasible to forward-port the patch to new minor releases (and micro releases.) However, upstream wants a more generic change in order to merge it: https://bugs.libssh.org/T27
-Mike
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
Hi Mike,
I was talking with my customer today. They tested X2Go Client for Windows with libssh-0.9.2 for about 3 weeks and are totally happy. Apparently this version increased the stability of X2Go client significantly. Before they got crashes with libssh error message "socket error: No error" once in several days for every user. In the case of X2Go connection over SSH Proxy every 3-4 connections(in this case client opens more SSH channels than in the case of the direct connection). Since they are using libssh-0.9.2 they didn't have this error any single time. I'll try to build the new version of libssh with pagent patch and will provide you a binaries. I think I'll have time for it this or next week. Would be grate if we can build an installer of X2Go client with libssh-0.9.2
regards Alex
Am 08.11.19 um 15:18 schrieb Oleksandr Shneyder:
Yes, but I don't have access to it now. I'll do it in 2 weeks. Till that moment we'll see how X2Go Client works with the library I built.
Am 07.11.19 um 17:16 schrieb Mike DePaulo:
If you already built 0.9.2 and have a build environment ready to go, would you be able to forward-port the patch, and share the patch / binaries with via the 2nd git repo I linked to?
On Thu, Nov 7, 2019 at 1:26 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Ok, I see. We don't need to rush, but we should think about upgrade of libssh one time. I think it's quite important to get rid of this annoying issue, when the X2Go Client crashes because of some bug in the libssh. I'll see the customer in 3 weeks again and will let you know how tests are going. Than we can talk about it again.
regards Alex
Am 07.11.19 um 12:16 schrieb Mike DePaulo:
On Thu, Nov 7, 2019 at 12:24 PM Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Hi,
who knows which version of libssh we are using with current Windows client? Last week I was on site of one of my customers and investigated the issue when X2Go Client on Windows 10 was not able to open SSH channel with libssh error "socket error: No error". Apparently customer has this problem sometimes, not very often. But in case, when customer opened a session over SSH proxy, he was able to reproduce the issue in every 3rd-4th connection. I tried to build several versions of libssh for testing. With 0.7.7 I was still able to reproduce such behavior. After that I built the most recent version (0.9.2). We're still testing it, but looks like we don't have this issue any more. So, I was thinking maybe we should update libssh library in our Windows client.
Still 0.7.4: https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=copy-deps-win32.bat https://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=tree;f=libssh
We still have to patch each version to use pageant (see the folder above). It has always been feasible to forward-port the patch to new minor releases (and micro releases.) However, upstream wants a more generic change in order to merge it: https://bugs.libssh.org/T27
-Mike
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
-
Mike DePaulo -
Oleksandr Shneyder