Lines Matching full:token

37 token-based record stream to represent system audit data.
42 BSM token streams typically begin and end with a
44 token, which provides time stamp and file name information for the stream;
45 when processing a BSM token stream from a stream as opposed to a single file
51 token, and ends with a
53 token, which describe the audit record.
58 The BSM file format defines specific token orders for each record event type;
62 This manual page documents the common token types and their binary format, and
68 .Ss File Token
71 token is used at the beginning and end of an audit log file to indicate
77 token can be created using
81 .It "Token ID	1 byte	Token ID"
87 .Ss Header Token
90 token is used to mark the beginning of a complete audit record, and includes
95 token can be created using
99 token can be created using
103 .It "Token ID	1 byte	Token ID"
111 .Ss Expanded Header Token
114 token is an expanded version of the
116 token, with the addition of a machine IPv4 or IPv6 address.
119 token can be created using
123 token can be created using
127 .It "Token ID	1 byte	Token ID"
137 .Ss Trailer Token
145 token can be created using
149 .It "Token ID	1 byte	Token ID"
153 .Ss Arbitrary Data Token
156 token contains a byte stream of opaque (untyped) data.
165 token can be created using
169 .It "Token ID	1 byte	Token ID"
175 .Ss in_addr Token
178 token holds a network byte order IPv4 address.
181 token can be created using
186 .It "Token ID	1 byte	Token ID"
189 .Ss Expanded in_addr Token
192 token holds a network byte order IPv4 or IPv6 address.
195 token can be created using
201 section for information on the storage of this token.
204 .It "Token ID	1 byte	Token ID"
208 .Ss ip Token
211 token contains an IP packet header in network byte order.
214 token can be created using
218 .It "Token ID	1 byte	Token ID"
230 .Ss iport Token
233 token stores an IP port number in network byte order.
236 token can be created using
240 .It "Token ID	1 byte	Token ID"
243 .Ss Path Token
246 token contains a pathname.
249 token can be created using
253 .It "Token ID	1 byte	Token ID"
257 .Ss path_attr Token
260 token contains a set of NUL-terminated path names.
265 token.
268 .It "Token ID	1 byte	Token ID"
269 .It "Count	2 bytes	Number of NUL-terminated string(s) in token"
272 .Ss Process Token
275 token contains a description of the security properties of a process
280 token, which describes the subject performing an auditable event.
287 token can be created using
293 .It "Token ID	1 byte	Token ID"
304 .Ss Expanded Process Token
307 token contains the contents of the
309 token, with the addition of a machine address type and variable length
313 token can be created using
319 .It "Token ID	1 byte	Token ID"
331 .Ss Return Token
334 token contains a system call or library function return condition, including
339 token can be created using
345 .It "Token ID	1 byte	Token ID"
349 .Ss Subject Token
352 token contains information on the subject performing the operation described
362 token can be created using
368 .It "Token ID	1 byte	Token ID"
379 .Ss Expanded Subject Token
382 token consists of the same elements as the
384 token, with the addition of type/length and variable size machine address
388 token can be created using
394 .It "Token ID	1 byte	Token ID"
406 .Ss System V IPC Token
409 token contains the System V IPC message handle, semaphore handle or shared
411 A System V IPC token may be created using
415 .It "Token ID	1 byte	Token ID"
419 .Ss Text Token
422 token contains a single NUL-terminated text string.
425 token may be created using
429 .It "Token ID	1 byte	Token ID"
433 .Ss Attribute Token
436 token describes the attributes of a file associated with the audit event.
444 token can be created using
450 .It "Token ID	1 byte	Token ID"
458 .Ss Groups Token
461 token contains a list of group IDs associated with the audit event.
464 token can be created using
468 .It "Token ID	1 byte	Token ID"
469 .It "Number of Groups	2 bytes	Number of groups in token"
472 .Ss System V IPC Permission Token
475 token contains a System V IPC access permissions.
476 A System V IPC permission token may be created using
480 .It "Token ID	1 byte	Token ID"
489 .Ss Arg Token
492 token contains information about arguments of the system call.
493 Depending on the size of the desired argument value, an Arg token may be
500 .It "Token ID	1 byte	Token ID"
506 .Ss exec_args Token
509 token contains information about arguments of the exec() system call.
510 An exec_args token may be created using
514 .It "Token ID	1 byte	Token ID"
518 .Ss exec_env Token
521 token contains current environment variables to an exec() system call.
522 An exec_args token may be created using
526 .It "Token ID	1 byte	Token ID"
530 .Ss Exit Token
533 token contains process exit/return code information.
536 token can be created using
540 .It "Token ID	1 byte	Token ID"
544 .Ss Socket Token
547 token contains information about UNIX domain and Internet sockets.
548 Each token has four or eight fields.
549 Depending on the type of socket, a socket token may be created using
556 .It Li "Token ID" Ta "1 byte" Ta "Token ID"
561 .Ss Expanded Socket Token
564 token contains information about IPv4 and IPv6 sockets.
567 token can be created using
571 .It Li "Token ID" Ta "1 byte" Ta "Token ID"
580 .Ss Seq Token
583 token contains a unique and monotonically increasing audit event sequence ID.
588 .It "Token ID	1 byte	Token ID"
591 .Ss privilege Token
594 token ...
597 .It "Token ID	1 byte	Token ID"
599 .Ss Use-of-auth Token
602 token ...
605 .It "Token ID	1 byte	Token ID"
607 .Ss Command Token
610 token ...
613 .It "Token ID	1 byte	Token ID"
615 .Ss ACL Token
618 token ...
621 .It "Token ID	1 byte	Token ID"
623 .Ss Zonename Token
626 token holds a NUL-terminated string with the name of the zone or jail from
630 token can be created using
634 .It "Token ID	1 byte	Token ID"
661 token has undefined values.
667 token layout documented here appears to be in conflict with the