Re: SSH, remote X-applications and 9.1

From: Jeremy Smith (please_post_to_group_at_avoidspam.net)
Date: 06/30/04


Date: Tue, 29 Jun 2004 20:49:25 -0400


It turns out, strange as it seems, that in order for the:

$DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN to "yes"

change to work, a reboot was actually necessary.

Restarting the X server (done via kdm at the login window) was not enough (I
read somewhere on the web that all you have to do is restart the X server).
I did try a reboot before, but apparently something else was different
too...

Just FYI.

Thanks,

~ Jeremy

Jeremy Smith wrote:

> I am experiencing the same issue... it really is not an SSH issue. The
> fact is, my machine, while running X (KDM) is not listening on the default
> X11
> window :0 port (6000). I verify this with "netstat -a"
>
> So, for me, ssh forwarding works fine, but no non-ssh-forwarded X traffic
> can get to my new SuSE 9.1 install.
>
> NOTE: ssh forwarding works unless you try to run a SETUID program.
> Then, because of xauth stuff (you are switching to a user that is
> not allowed to forward the X traffic), you get this error:
>
> X11 connection rejected because of wrong authentication.
> X connection to localhost:10.0 broken (explicit kill or server
> shutdown).
>
> Now, I have been on google and read that you need to use yast's sysconfig
> editor to change:
> $DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN to "yes" (DEFAULT is "no")
> And I've done that. I didn't hand-edit. I restarted my X server (and
> even
> tried rebooting ugh). Still no good.
>
> Because of the setuid auth issues, I need to allow X connections on port
> 6000 and do as Dana does below.
>
> Dana, have you set $DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN to "yes"?
> If not, try that and please let us know if it worked.
>
> Everybody else: Any insight into why _I_ still am not listening on 6000?
>
> Thanks!
>
> ~ Jeremy
>
>
>
> Dana Wellen wrote:
>
>> connect? Normally I would;
>>
>> xhost +
>> telent remote-system
>> {login}
>> setenv DISPLAY {Xserver}:0
>> run X-application
>>
>> Until 9.1 there wasn't any problem doing this, with 9.1 no matter what I
>> have tried, nothing disables this protection.
>>
>> Thanks,
>> Dana Wellen



Relevant Pages

  • Re: How Frequent to Reboot Server Best Practices?
    ... > to reboot a Windows Server 2003? ... If a server has to be rebooted on a scheduled basis for other than patches ... restarting of processes that grow too large over time. ... cheers when Linux panics or BSD dumps core! ...
    (microsoft.public.windows.server.general)
  • Re: Windows Server 2003 SP2
    ... Can I get rid of it now, before restarting? ... you probably want to plan the reboot expecting troubles. ... Windows Server 2003 SP2. ...
    (microsoft.public.windows.server.sbs)
  • Re: Printers in TS
    ... Aaron ... > Instead of restarting your server, ... >> reboot of the server. ...
    (microsoft.public.windows.terminal_services)
  • Re: Printers in TS
    ... Instead of restarting your server, ... > (printername on PC session #). ... > reboot of the server. ...
    (microsoft.public.windows.terminal_services)
  • Another disaster recovery exercise (but not yet)...
    ... I updated a client's Server. ... indeed, I reboot before updating, and after ). ... Chkdsk is all good on all drives. ... Enabling boot logging option at boot - well, ...
    (microsoft.public.backoffice.smallbiz2000)