Prev: network mirror
Next: Sudden X11 forwarding glitch - Can't open display"localhost:10.0"
From: Mike Jones on 7 Feb 2010 15:54


I've no idea what happened, but something is barfing my X11 forwarding
all of a sudden. I'm getting Can't open display "localhost:10.0" for

ssh -Y 192.168.1.1 X11app

Everything else works fine, console apps like Lynx, nano, etc. Its just
the X11 apps that can't seen to get hold of the X11 display, even though
everything worked fine a week ago (confirmed by client-machine use). The
problem seems to be located on the server box as all clients and all
accounts on the LAN are affected the same, no X11 apps suddenly.

Where should I start looking for problems on this one? I've been checking
through looking for any hack-glitches I might have introduced over the
last week (since this problem appeared), but I can't recall fiddling with
anything X11 or ssh related for while now.

Puzzled.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: allend on 7 Feb 2010 17:18
Do you have X11 forwarding turned on in /etc/ssh/sshd_config on the
server?
Either globally:
X11Forwarding yes
or:
per user
Match User <username>
X11Forwarding yes
Match

From: Mike Jones on 7 Feb 2010 18:28
Responding to allend:

> Do you have X11 forwarding turned on in /etc/ssh/sshd_config on the
> server?
> Either globally:
> X11Forwarding yes
> or:
> per user
> Match User <username>
> X11Forwarding yes
> Match


Yup, all just as it was last week when everything worked fine.

I'm a bit stuck as to what happened, and I'm suspecting that my server's
MOBO might be terminally borked. Its had a rough life and does a few
other odd things every so often. This is my last fault-investigation
before I commit cash to a new MOBO, so I need to make sure it is hardware
and not something I'm going to slap my head over the week after spending
money.

I guess due to the lack of "Oh yeah! That happend to me, and..."
responses that it might indeed be hardware related. I've never heard of a
slackware system glitching like this.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Henrik Carlqvist on 8 Feb 2010 02:16
Mike Jones <Not(a)Arizona.Bay> wrote:
> I've no idea what happened, but something is barfing my X11 forwarding
> all of a sudden. I'm getting Can't open display "localhost:10.0"

Do you have your home directory on an NFS file system? Does some of your
machines in the LAN run kernel 2.6.24 or newer? If so, you might have been
bitten by a kernel bug: http://bugzilla.kernel.org/show_bug.cgi?id=12557

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Henrik Carlqvist on 8 Feb 2010 02:22
"Aaron W. Hsu" <arcfide(a)sacrideo.us> wrote:
> I see a lot of people using the -Y option,

Many X applications crash with error messages about bad atoms when using
the -X option.

> but from everything that I've read and heard, that's asking for trouble, as
> none of the appropriate security measures are taken to ensure that you
> have a secure connection.

The connection is just as encrypted and safe with -Y as with -X. The big
difference is that you with -Y will have to trust the remote machine more.
Someone with root access on the remote machine might be able to start X
applications on your display from that remote machine if you are using the
-Y switch, the -X switch prevents this in newser versions of openssh.
Those applications started by root could include bad applications that
takes screen shots and logs keys from your display.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

 |  Next  |  Last
Pages: 1 2 3 4
Prev: network mirror
Next: Sudden X11 forwarding glitch - Can't open display"localhost:10.0"