Re: [X2Go-Dev] Bug in sshproxy handling

2019-06-16 Thread Mihai Moldovan
* On 5/17/19 10:51 PM, Ulrich Sibiller wrote: > On Fri, May 17, 2019 at 9:31 PM Ulrich Sibiller > wrote: >> Alternatively we could add a hack: if the proxy hostname has some >> special form, e.g. "!hostname", that very check will be skipped. As >> proxy and normal hosts are both controlled via

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Oleksandr Shneyder
Hi Uli, I could leave with this "hack". I think we can take your patches in the x2go client source. regards, Alex Am 17.05.19 um 15:51 schrieb Ulrich Sibiller: > On Fri, May 17, 2019 at 9:31 PM Ulrich Sibiller > wrote: >> Alternatively we could add a hack: if the proxy hostname has some >>

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Ulrich Sibiller
On Fri, May 17, 2019 at 9:31 PM Ulrich Sibiller wrote: > Alternatively we could add a hack: if the proxy hostname has some > special form, e.g. "!hostname", that very check will be skipped. As > proxy and normal hosts are both controlled via the same code in > SshmasterConnection this way the

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Ulrich Sibiller
On Fri, May 17, 2019 at 5:06 PM Oleksandr Shneyder wrote: > > >> technically it's a very simple solution. However I'm not sure if it > >> worth to make UI more complicated and loaded with features which are > >> required only by one untypical setup. One thing here is that it used to work and

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Oleksandr Shneyder
would be OK for me, but it'll require more user experience for the client configuration. For Windows users even more, they'll need to edit windows registry. Am 17.05.19 um 09:44 schrieb Stefan Baur: > Am 17.05.19 um 16:39 schrieb Oleksandr Shneyder: >> technically it's a very simple solution.

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Stefan Baur
Am 17.05.19 um 16:39 schrieb Oleksandr Shneyder: > technically it's a very simple solution. However I'm not sure if it > worth to make UI more complicated and loaded with features which are > required only by one untypical setup. > On this place I would like to ask the list members if some one has

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Oleksandr Shneyder
Am 17.05.19 um 08:55 schrieb Ulrich Sibiller: > On Fri, May 17, 2019 at 3:48 PM Oleksandr Shneyder > wrote: >> It's not only about updating the user passwords. This kind interaction >> could be used for 2-factor authentication and in many other cases. There >> are many possible cases when server

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Oleksandr Shneyder
Hello Uli, It's not only about updating the user passwords. This kind interaction could be used for 2-factor authentication and in many other cases. There are many possible cases when server needs to have some additional interaction with user and updating of passwords is only one of them. After

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-17 Thread Ulrich Sibiller
On Fri, May 17, 2019 at 3:48 PM Oleksandr Shneyder wrote: > It's not only about updating the user passwords. This kind interaction > could be used for 2-factor authentication and in many other cases. There > are many possible cases when server needs to have some additional > interaction with user

Re: [X2Go-Dev] Bug in sshproxy handling

2019-05-16 Thread Ulrich Sibiller
> log looks the same. I think that login check is issuing a command on > the proxy to check if the proxy is working ("echo LOGIN OK"). And due > to the nature of our gateway (see above) this fails, because it is an > invalid command. > > Unfortunately I don't really see if this assumption is

[X2Go-Dev] Bug in sshproxy handling

2019-05-16 Thread Ulrich Sibiller
Hi, some time ago I have successfully set up the x2goclient 4.1.0.0 for Windows to access some Linux machines via an ssh security gateway. It worked fine. Yesterday I wanted to use that connection with x2gclient 4.1.2.0 and it failed. Today I have tracked this down a bit more and can report this