I just upgraded my office machine to Jaguar and am no longer able to run
X-apps from home due to X-forwarding problems.
I've set ForwardX11 to yes in both /etc/ssh_config and (after installing
openssh from fink) in /sw/etc/ssh/ssh_config. I've also tried logging
in with
ssh -X [EMAIL PROTECTE
in /sw/etc/ssh/sshd_config and /etc/sshd_config
X11Forwarding yes
all other values as installed.
Another possible culprit (I need to check) are the MATLAB-installed
changes to X11R6 under Jaguar. I did a re-install of X11R6 while at
work tonight; I'll try it out again when I get home to see i
Thanks. Neither than nor my Matlab X11R6 patch idea seemed to have any
effect.
On Sunday, November 3, 2002, at 03:12 AM, Hisashi T Fujinaka wrote:
I usually start deleting .Xauthority until things work.
On Sun, 3 Nov 2002 [EMAIL PROTECTED] wrote:
in /sw/etc/ssh/sshd_config and /etc/sshd_conf
ssh -X -v -v -v ${mymachine} yields;
[skipped output not related to X11]
debug2: x11_get_proto /usr/X11R6/bin/xauth list :0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug1: channel request 0: x11-req
debug1: channel request 0: shell
debug1: fd 3 setting TCP_NODE
Stupid questions are often the most valuable; yes, I did check that
DISPLAY was set on my
home machine (I can never get "client" and "Server" straight in my head,
but I think this is
the server, the physical display, and DISPLAY is set to :0
[localhost:~] hodelas% echo $D
[mymachine:~] hodelas% find .[a-z]* -type f -exec grep DISPLAY {} \;
-print
echo $DISPLAY
.bash_history
echo $DISPLAY
.tcsh_history
.cshrc only souces /sw/bin/init.csh, so I'm at a loss of where else to
look.
On Monday, November 4, 2002, at 01:58 AM, Hisashi T Fujinaka wrote:
And now t
start the
daemon manually with 'sudo /sw/sbin/sshd -ddd' and watch out for debug
messages on the server side.
It looks like I'll have to try the diagnostic output of sshd:
[mymachine:~] hodelas% which sshd
/sw/sbin/sshd
Aha! I should have seen this before:
hodelas% ps x | grep ssh
n manually with 'sudo /sw/sbin/sshd -ddd' and watch out
for debug messages on the server side.
This appears to be a part of the problem:
[mymachine:~] hodelas% /sw/sbin/sshd -ddd
debug1: sshd version OpenSSH_3.5p1
Could not load host key: /sw/etc/ssh/ssh_host_key
Could not load h