Re: X11 forwarding stops after 10.8 upgrade
Re: X11 forwarding stops after 10.8 upgrade
- Subject: Re: X11 forwarding stops after 10.8 upgrade
- From: Jeremy Huddleston Sequoia <email@hidden>
- Date: Fri, 27 Jul 2012 09:28:49 -0700
On Jul 27, 2012, at 8:28 AM, Martin Costabel <email@hidden> wrote:
> On 27/07/12 16:57, Chris Jones wrote:
>> Hi,
>>
>> Indeed, adding the line
>>
>> XauthLocation /opt/X11/bin/xauth
>>
>> to the /etc/sshd_config file on the remote machine, seems to have worked
>> around the issue.
>
> I confirm. If I add the line
>
> XauthLocation /usr/X11R6/bin/xauth
>
> it works also. It still gives the lines
>
> debug1: No xauth program.
> Warning: No xauth data; using fake authentication data for X11 forwarding.
> debug1: Requesting X11 forwarding with authentication spoofing.
>
> but then it connects OK, with X11 forwarding.
>
> But this should not be necessary. According to man sshd_config:
>
> XAuthLocation
> Specifies the full pathname of the xauth(1) program. The default is /usr/X11R6/bin/xauth.
>
> Something fishy here, at least sshd_config is lying about the default.
Ok, I think that explains the issue then.
In Mountain Lion, we got rid of X11. As part of that, we provided a stub X11.app and /usr/X11/bin which would cause a notification to be presented to the user. ssh used to execute /usr/X11/bin/xauth (which would cause the notification to be displayed whenever a user ssh'd to a remote system). This was replaced by searching $PATH for xauth (see ssh_config(5)). This works fine on the client side, but it looks like it has an issue on the server side because /opt/X11/bin isn't in the server's $PATH.
Try placing an xauth symlink in /usr/local/bin, so it will be in sshd's $PATH ... I might be able to add that symlink with XQuartz 2.7.3.
--Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden