Lines Matching full:cookie
792 <entry>The serial of this message, used as a cookie
1685 <title>Example of successful magic cookie authentication</title>
1761 <title>Example of successful magic cookie authentication with successful negotiation of Unix FD passing</title>
1773 <title>Example of successful magic cookie authentication with unsuccessful negotiation of Unix FD passing</title>
2189 cookie stored in this file, then the client is authenticated.
2209 The server sends the name of its "cookie context" (see below); a
2210 space character; the integer ID of the secret cookie the client
2218 The client locates the cookie and generates its own
2221 another ":" character, and the cookie. It computes the SHA-1 hash
2238 Each server has a "cookie context," which is a name that identifies a
2252 contains cookie files named after the cookie context.
2255 A cookie file contains one cookie per line. Each line
2260 The cookie ID number, which must be a non-negative integer and
2266 The cookie's creation time, in UNIX seconds-since-the-epoch
2272 The cookie itself, a hex-encoded random block of bytes. The cookie
2280 Only server processes modify the cookie file.
2286 cookie file. The server should attempt to create this file
2299 Once the lockfile has been created, the server loads the cookie
2310 The pruned and possibly added-to cookie file
