Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!pacbell.com!ames!sheba.arc.nasa.gov!schoch
From: schoch@sheba.arc.nasa.gov (Steve Schoch)
Newsgroups: comp.windows.x
Subject: Re: locking out users from a server....
Keywords: X11R4.18, SunOS, xinit  Dam* students anyway...
Message-ID: <1990Nov1.180206.26574@news.arc.nasa.gov>
Date: 1 Nov 90 18:02:06 GMT
References: <8974@ncar.ucar.edu> <1990Oct30.205926.28985@news.arc.nasa.gov> <1990Oct31.000115.26078@Think.COM>
Sender: usenet@news.arc.nasa.gov (USENET Administration)
Reply-To: schoch@sheba.arc.nasa.gov (Steve Schoch)
Organization: NASA Ames Research Center, Moffett Field, CA
Lines: 16

In article <1990Oct31.000115.26078@Think.COM>, barmar@think.com (Barry Margolin) writes:
|> Does this mean that MIT-MAGIC-COOKIE-1 authorization can only be used when
|> the server is running on the same host as xdm?  What is done for X
|> terminals and other random X servers?

An X terminal will get the authorization scheme and the authorization data
(the cookie) from xdm on a remote host using XDMCP (X Display Manager Control
Protocol?).  As part of the XDMCP handshaking, the server will tell xdm
which authorization schemes it supports and then xdm will tell the display
which one to use (obviously both the server and xdm must support it) and
the data to use with it.

I found this by reading the source, but the information is also availiable
in mit/doc/XDMCP.

	Steve