The examples in this article all use arguments.
13.9
184 Chapter 13: Remote Access
To see the current magic cookies and the display associated with each token, use the
xauth list command:
blue$ xauth list
blue/unix:0 MIT-MAGIC-COOKIE-1 63fa4c416da8b8c5b4d3ae32b3206486
blue:0 MIT-MAGIC-COOKIE-1 63fa4c416da8b8c5b4d3ae32b3206486
green:3 MIT-MAGIC-COOKIE-1 35abebfef1c159b75783a4f33e2610fd
orange:1 MIT-MAGIC-COOKIE-1 b6577a2f2b7af4d82a1321779468cd0f
In this case, there are two entries for the local machine blue: the first one is for Unix
domain socket connections, and the second is for TCP/IP connections. The token
value is identical (63fa4c416da8b8c5b4d3ae32b3206486 in each case). The syntax for
the Unix domain socket in the xauth output (blue/unix:0 in this example) is slightly
different from a normal displayspec (which would be :0). The last two entries in the
output above are for displays on other hosts.
You may see some entries that use the XDM-AUTHORIZATION-1 protocol; this is a
variation on the magic cookie scheme that doesn??™t pass the token across the network
in plaintext, and it is used by display managers.
You can view the magic cookie for one display by specifying a displayspec:
blue$ xauth list :0
blue/unix:0 MIT-MAGIC-COOKIE-1 63fa4c416da8b8c5b4d3ae32b3206486
If a client on red is going to connect to display :0 on blue, the magic cookie for that
display needs to be placed into the ~/.
Pages:
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285