Posted by Daniel Tryba on 07/07/05 03:12

brian.vincent@gmail.com wrote:
> Now, maybe if I tell you the Big Picture idea you can think of another
> way to do it. I'm basically trying to create an application server. A
> user will need to authenticate and once they do so it will
> automatically fire up a graphical app residing on the remote server and
> display it back on the client. The apps need to utilize custom
> settings based on the user, so using something like ssh2_shell to
> execute it seems to a logical way to do it.
>
> Thanks for thinking about this so far. I'm somewhat stumped.

Me too, after an "xhost +" (which is offcourse BAD (ssh-ing into an
account that has any valid X display should be enough for your
solution)) any input should be allowed.

The only small difference I can think of might be that if you run the
commands yourself you are actually getting the results by tunneling the
X protocol so the effect will be that remote xclients effectively
connect to "localhost". Your httpd doesn't have a valid display so any
ssh session started from it will lack the X forwarding, if you try to
display to a remote machine it should talk to it thru the usual TCP
networking protocol. In many cases the Xserver will be started by
[xkg]dm, some installations (eg Debian) will disable tcp support in the
Xserver so that remote hosts can't connect with a simple
"-display remote:0.0". Scan for '-nolisten tcp' to see if this might be
the cause.

If this isn't it, I can't think of anything else :)

[Back to original message]