• 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: No xauth data; using fake authentication data
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: No xauth data; using fake authentication data


  • Subject: Re: No xauth data; using fake authentication data
  • From: Jeremy Huddleston <email@hidden>
  • Date: Tue, 23 Mar 2010 20:12:21 -0700

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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list      (email@hidden)

This email sent to email@hidden

References: 
 >No xauth data; using fake authentication data (From: Doug Carter <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: Marco S Hyman <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: dp <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: dp <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: dp <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: Jonas Maebe <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: dp <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: Doug Carter <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: Jeremy Huddleston <email@hidden>)
 >Re: No xauth data; using fake authentication data (From: dp <email@hidden>)

  • Prev by Date: Re: No xauth data; using fake authentication data
  • Next by Date: Re: No xauth data; using fake authentication data
  • Previous by thread: Re: No xauth data; using fake authentication data
  • Next by thread: Re: No xauth data; using fake authentication data
  • Index(es):
    • Date
    • Thread