Xauthority file on red. Sharing the home directories
via NFS will take care of this automatically; otherwise, this can be done with
xauth??™s add command, which accepts a displayspec, protocol, and token value as
arguments:
red$ xauth add blue:0 MIT-MAGIC-COOKIE-1 63fa4c416da8b8c5b4d3ae32b3206486
red$ xauth list blue:0
blue:0 MIT-MAGIC-COOKIE-1 63fa4c416da8b8c5b4d3ae32b3206486
It??™s a pain typing in MIT-MAGIC-COOKIE-1 all the time, so xauth permits you to substitute
the period character (.); therefore, the preceding add command could be rewritten
as:
red$ xauth add blue:0 . 63fa4c416da8b8c5b4d3ae32b3206486
You can also use xauth to create an extract file, which can be sent to another
machine and merged into the ~/.Xauth file there:
blue$ xauth extract extractfile blue:0
...transfer extractfile from the host blue to red using the file
tranfer mechanism of your choice...
red$ xauth merge extractfile
13.9
13.9 xauth and Magic Cookies 185
Obviously, transporting cookies between hosts is a big nuisance.
Don??™t despair; the process can be automated using SSH (Section
13.12).
Once the magic cookie has been copied to the remote machine (red), clients started
there will be able to successfully connect to the X server regardless of the current
host-based authentication settings (Section 13.
Pages:
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286