Thanks for the reply Dale.

I have learned the hard way that sshd cannot be restarted remotely (sshd
does not respond to HUP). Apparently, sshd forks a new sshd process
when a new connection is made and the new sshd process reads the config
file anew. Therefore, there shouldn't be any need to restart.

Can anyone confirm this? I've never truly found the definitive answer
for this.

-----Original Message-----
From: Foster, Dale [mailto:dale.foster@eds.com]=20
Sent: Tuesday, April 19, 2005 10:21 AM
To: Christ, Bryan
Subject: RE: X11 Forwarding

Have you restarted the sshd since setting "X11Forwarding" to yes?

Once you log into the "host", what does "echo $DISPLAY" report?

-----Original Message-----
From: Christ, Bryan [mailto:bryan.christ@hp.com]
Sent: April 18, 2005 8:46 AM
To: secureshell@securityfocus.com
Subject: X11 Forwarding


Does anyone know why my DISPLAY variable is not getting set? I have
tried looking at the debug messages from

ssh -vv -X user@host

but I haven't seen anything suspicious. xauth is installed in the normal
location and seems to run correctly (although I'm really not familiar
with it). In my sshd_config file, the relevant options are set as:

X11Forwarding yes
X11DisplayOffset 10
#X11UseLocalHost no
#UseLogin yes

I've spent quite a bit of time googling on this problem and haven't come
up with anything yet. I suspect that it might have something to do with
installing XFree86 on Slackware 9.0 after initial OS installation (using
installpkg *.tgz on the relevant packages). I'm really at a loss for
where to turn.

Server is OpenSSH 3.5p1, OpenSSL 0.9.7a
Client is OpenSSH 4.0p1, OpenSSL 0.9.7f=20

Thanks in advance!