On Fri, May 17, 2019 at 5:06 PM Oleksandr Shneyder
<o.shney...@phoca-gmbh.de> 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 stopped beginning with
4.1.1.1. So the correct solution would have been to leave the old
default and add an UI option that enables the new behaviour.  But as
noone has complained the past year we can safely assume that noone is
having problems with the new behaviour.

> >> On this place I would like to ask the list members if some one has a
> >> same usecase or would find this feature useful.

> > How about not adding an UI item but merely a config file option?

> 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.

Yeah, but as I am the first one to notice this chances are noone else
will ever need this... So having to configure that in a cumbersome way
might be ok.

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 user could configure that for both
connections independently.

Third option was to add a command line option that simply deactivates
the check. This would account for all session and for proxy and
non-prpoxy session, but again: not mayn people will ever need this.

Fourth option was to make the command (and its expected result) that
is used to check for interactivity ("echo "LOGIN OK"") configurable.
An empty value will then skip the check.

Alex, are you aware of setup that require the LOGIN OK check? Do you
have access to such a system? Maybe we can find another indicator that
makes the check obsolete.

Uli
_______________________________________________
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

Reply via email to