• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Accessing RedHat Linux 8 system
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Accessing RedHat Linux 8 system


  • Subject: Re: Accessing RedHat Linux 8 system
  • From: bryan <email@hidden>
  • Date: Thu, 27 Feb 2003 09:40:09 +1300

On Wednesday, February 26, 2003, at 10:02  PM, Jonas Maebe wrote:

On woensdag, feb 26, 2003, at 06:05 Europe/Brussels, bryan wrote:

Same sort of problem here (I think) on LinuxPPC. Beige G3 266:

habanero	=Mac OS X 10.2.4 w/ X11 (second beta)
ecstasy		=LinuxPPC 2000 Q4

[habanero:~] bryan% ssh -X ecstasy uname -a

Are you doing this from inside an XTerm or from within Terminal? In the latter case, you first have to do a


setenv DISPLAY :0

ssh-ing from xterm (now. -see below).


(if you're using the default tcsh, for bash it's "export DISPLAY=:0").

Linux ecstasy 2.2.18-4hpmac #1 Thu Dec 21 15:16:15 MST 2000 ppc unknown

[habanero:~] bryan% ssh -X ecstasy /usr/bin/same-gnome
connect habanero port 6000: Connection refused

I think this shows that "same-gnome" is not using the ssh tunnel, since it would not try to connect to port 6000 of habanero in that case.

This was my bad. I didn't have X11 running on this occasion. although I am still having problems...see the error below....


Gdk-ERROR **: X connection to ecstasy:10.0 broken (explicit kill or server shutdown).

I asked a while ago but got no replies as X11 the second beta had just been released.

My best guess is that everyone thought that maybe the problem was fixed in this new version....


This is the error that should be above (If I had been paying attention like a good little boy)
habanero =Mac OS X 10.2.4 w/ X11 (second beta)
ecstasy =LinuxPPC


		#show display set on Mac OS X/X11 (from xterm)
[habanero:~] bryan% env | grep DISPLAY
DISPLAY=habanero:0.0

#when the remote application is specified with the ssh command it appears as you would expect.
[habanero:~] bryan% ssh -X ecstasy /usr/bin/same-gnome &
[1] 3831


		#show display set on ecstasy/LinuxPPC
[habanero:~] bryan% ssh -X ecstasy
[bryan@ecstasy bryan]$ env | grep DISPLAY
DISPLAY=ecstasy:10.0

#when the remote application is specified after ssh login the error below appears.
[bryan@ecstasy bryan]$ /usr/bin/same-gnome &
[1] 9682
[bryan@ecstasy bryan]$ X11 connection rejected because of wrong authentication.
Gdk-ERROR **: X connection to ecstasy:10.0 broken (explicit kill or server shutdown).


												#and now we control c to end the failed app.
[1]+  Exit 1                  /usr/bin/same-gnome
[bryan@ecstasy bryan]$


Nothing was broken in the first release regarding ssh forwarding and it's still not broken in the second release. This kind of problems is almost always due to configuration issues. The most likely causes are

a) "X11Forwarding yes" is not set in the /etc/sshd_config file of the machine you are ssh'ing to

[bryan@ecstasy bryan]$ sudo grep X11Forwarding /etc/ssh/sshd_config Password: X11Forwarding yes [bryan@ecstasy bryan]$

b) you have *not* set the DISPLAY environment variable to :0 or didn't start X11.app on the local machine before you ssh'd to the remote host (the fact that X11.app must already be started is strange, because I seem to remember that this was not necessary for XDarwin)
Got this (now) -see above

c) you *do* set the DISPLAY environment variable in a login script on the remote server, so it overrides the one ssh has set
Nope.

[bryan@ecstasy bryan]$ env | grep DISPLAY
DISPLAY=ecstasy:10.0


d) (very unlikely in this case) you are trying to run a very old X program and are using sshd 3.1 (or maybe even 3.0, I don't remember) or higher on the remote server. In that case, you have to add "X11UseLocalhost no" to the sshd_config on the remote machine. Note that adding this option is potentially more insecure (though there are no known exploits afaik) that the default setting of "yes".

I have tried a few programs and they all work if i specify them on the command line with my ssh login, but fail if specified after I have loged in and are attempting to execute from the remote shell.
my ssh version...


[bryan@ecstasy bryan]$ ssh -version
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090581f


-bryan. _______________________________________________ x11-users mailing list | email@hidden Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html Report issues, request features, feedback: http://developer.apple.com/bugreporter Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Accessing RedHat Linux 8 system
      • From: Jonas Maebe <email@hidden>
References: 
 >Re: Accessing RedHat Linux 8 system (From: Jonas Maebe <email@hidden>)

  • Prev by Date: Re: .X0-lock and .X11-unix/
  • Next by Date: [x11-users] Launching X11 apps from Aqua?
  • Previous by thread: Re: Accessing RedHat Linux 8 system
  • Next by thread: Re: Accessing RedHat Linux 8 system
  • Index(es):
    • Date
    • Thread