Re: No xauth data; using fake authentication data
Re: No xauth data; using fake authentication data
- Subject: Re: No xauth data; using fake authentication data
- From: Jeremy Huddleston <email@hidden>
- Date: Mon, 3 Jan 2011 10:30:11 -0800
I think OpenSSH was patched to work better with X11's launchd socket a few months ago... try grabbbing their latest svn/git/whatever
On Jan 2, 2011, at 18:09, Charles Antonelli wrote:
> As the message is annoying, albeit benign, I'd suggest something like:
>
> --- clientloop.c- 2010-08-03 02:04:46.000000000 -0400
> +++ clientloop.c 2011-01-02 19:57:44.000000000 -0500
> @@ -391,7 +391,7 @@
> if (!got_data) {
> u_int32_t rnd = 0;
>
> - logit("Warning: No xauth data; "
> + verbose("Warning: No xauth data; "
> "using fake authentication data for X11 forwarding.");
> strlcpy(proto, SSH_X11_PROTO, sizeof proto);
> for (i = 0; i < 16; i++) {
>
> Charles
>
> On Mar 23, 2010, at 19:37, dp wrote:
>
>> On 3/23/10 7:05 PM, Jeremy Huddleston wrote:
>>>
>>> On Mar 23, 2010, at 09:59, Doug Carter wrote:
>>>> The workaround is to find the display number X is using, in my case ":3"
>>>> and set the DISPLAY variable to it:
>>>>
>>>> export DISPLAY=:3
>>>>
>>>> After making these changes, the warning message goes away.
>>>
>>> Please don't do that.
>>>
>>> The message is benign. Just ignore it.
>>>
>>> The reason for this message is that when making the connection, the ssh client checks xauth for authentication information for your $DISPLAY. Assuming it is set, it then passes that along to your session on the remote system.
>>>
>>> Using the launchd socket, there is no match in ~/.Xauthority. That is by design. The launchd socket is only accessible by you as designed by launchd. As such, there is no need to create an entry in ~/.Xauthority for it nor to authenticate that connection using xauth.
>>
>> Thanks, Jeremy - what caused this to start showing up now? The message itself is not important as it is what you say, but the sudden appearance is generating wonderment.
>
> The only thing that makes sense to me would be the change of the $DISPLAY to include an identifier that says which server it belongs to... maybe ssh previously ignored something of the format:
> /tmp/launch-ATqbAa/:0
>
> versus the current:
> /tmp/launch-ATqbAa/org.macosforge.xquartz:0
>
> or maybe it was getting a false-hit in its search of the xauth data before...
>
> I dunno... either way, it's something easily ignored. I'm curious about why it might've suddenly appeared with the new $DISPLAY format, but since it is a benign warning, and I have tons of other things to worry about, I won't be giving it much additional though.
>
> --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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden