DRI2 Protocol Spec Draft

[Keith Packard]

On Wed, 2008-09-10 at 17:28 -0400, Kristian Høgsberg wrote:

> No that's why the existing scheme is better, it doesn't rely on
> random/cryptographical tokens.  It just needs to be a unique handle
> that lets the server identify the right client to authenticate.  If
> you can pass this token to the X server you're authenticated.  What
> better way to establish that than, erh, passing it through protocol?
> The key point is that the server does the ioctl that authenticates the
> client.

Ok, so the kernel generates a unique token that identifies the client
which the client takes and hands to the X server to pass back into the
kernel to authorize the client.

Just trying to figure out how this stuff is supposed to work.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20080910/94d8a7c1/attachment.pgp>