Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!bloom-beacon!dont-send-mail-to-path-lines
From: stripes@eng.umd.EDU ("Stripes ", or Josh, if you must)
Newsgroups: comp.windows.x
Subject: Re: Unix security additions
Message-ID: <9103262336.AA18783@egypt.eng.umd.edu>
Date: 26 Mar 91 23:36:21 GMT
References: <9103262132.AA22287@devnull.Eng.Sun.COM>
Sender: tytso@athena.mit.edu (Theodore Y. Ts'o)
Organization: The Internet
Lines: 31


David Rosenthal said:
>This is not correct.  To quote from the protocol spec Section 1 [page 370
>of the Digital Press 2nd edition]:
>
>	Every event contains an 8-bit type code.  The most-significant
>	bit in this code is set if the event was generated from a
>	SendEvent request.
>
>In other words,  there is only one bit of information transferred from the
>server to the client,  not a 16 or 32-bit field whose value could be used.

I guess I had forgotten.  (I have read the RFC, and the DP book, don't rember
which Ed)  I'll be reading Book 0 of the O'Reilly X seires again soon...
I guess if I had started it a few days ago I wouldn't have messed up :-(

>General comment.  When making claims about what X does or does not do,
>please do not depend on the arguments to the Xlib functions.  Read
>the protocol specification to make sure what the real information
>transferred between the server and the client is.

I try to, I just happen to read Xlib specs more offen, and use 'em more.
(this will change soon...)  In fact I knew the client got 32 bits (an int,
which is normally 32), and knew it wasn't 32, but for some reason I thought
it was 16, not 1.  *SIGH*
-- 
           stripes@eng.umd.edu          "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
"CNN is the only nuclear capable news network..."
    - lbruck@eng.umd.edu (Lewis Bruck)