Your message dated Fri, 12 Aug 2011 15:40:03 +0200
with message-id <1313156403.24704.452.camel@pi0307572>
and subject line Not a bug
has caused the Debian Bug report #637530,
regarding gdm3/gnome2: Failure of remote X server using ssh X11 forwarding
function
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
637530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637530
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome2
Version: gnome2 or gdm3
Severity: wishlist
-- System Information:
Debian Release: 6.0.2
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
The default flag "DisallowTCP=true" of gdm3 or gnome-desktop-environment makes
impossible to do remote X client through ssh -X.
ssh -X [email protected] login in the server.
Any Xorg that uses DISPLAY values will complain
"Can't open display."
There is no error between sshd and ssh.
The problem exists in gnome2 client side. Because gnome2 doesn't send TCP/IP
data related to
Xorg of the client, the client can not execute Xorg programs in X server.
Detail information is on the link.
http://forums.debian.net/viewtopic.php?f=6&t=68319
It needs to be informed to gnome2 or ssh users somehow to prevent
unnecessary time for troubleshooting this error.
Technically, I don't think it's not a bug.
gnome2 and ssh, sshd are doing exactly what they suppose to do based on
the configuration.
--- End Message ---
--- Begin Message ---
As you pointed out in the original report, this is not a bug. Using X11
on TCP is a huge security hole, which is why this is disabled.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--- End Message ---
