InomHitta mer dokumentationSupportresurser som ingår | Ladda ner denna bok i PDF (3065 KB)
audit.log(4)Name | Synopsis | Description | Attributes | See Also | Notes Name
Synopsis#include <bsm/audit.h> #include <bsm/audit_record.h> Descriptionaudit.log files are the depository for audit records stored locally or on an on an NFS-mounted audit server. These files are kept in directories named in the file audit_control(4) using the dir option. They are named to reflect the time they are created and are, when possible, renamed to reflect the time they are closed as well. The name takes the form yyyymmddhhmmss.not_terminated.hostname when open or if the auditd(1M) terminated ungracefully, and the form yyyymmddhhmmss.yyyymmddhhmmss.hostname when properly closed. yyyy is the year, mm the month, dd day in the month, hh hour in the day, mm minute in the hour, and ss second in the minute. All fields are of fixed width. Audit data is generated in the binary format described below; the default for Solaris audit is binary format. See audit_syslog(5) for an alternate data format. The audit.log file begins with a standalone file token and typically ends with one also. The beginning file token records the pathname of the previous audit file, while the ending file token records the pathname of the next audit file. If the file name is NULL the appropriate path was unavailable. The audit.log files contains audit records. Each audit record is made up of audit tokens. Each record contains a header token followed by various data tokens. Depending on the audit policy in place by auditon(2), optional other tokens such as trailers or sequences may be included. The tokens are defined as follows: The file token consists of:
The header token consists of:
The expanded header token consists of:
The trailer token consists of:
The arbitrary data token is defined:
The in_addr token consists of:
The expanded in_addr token consists of:
The ip token consists of:
The expanded ip token consists of:
The iport token consists of:
The path token consists of:
The path_attr token consists of:
The process token consists of:
The expanded process token consists of:
The return token consists of:
The subject token consists of:
The expanded subject token consists of:
The System V IPC token consists of:
The text token consists of:
The attribute token consists of:
The groups token consists of:
The System V IPC permission token consists of:
The arg token consists of:
The exec_args token consists of:
The exec_env token consists of:
The exit token consists of:
The socket token consists of:
The expanded socket token consists of:
The seq token consists of:
The privilege token consists of: token ID 1 byte text length 2 bytes privilege set name N bytes + 1 terminating NULL byte text length 2 bytes list of privileges N bytes + 1 terminating NULL byte The use-of-auth token consists of: token ID 1 byte text length 2 bytes authorization(s) N bytes + 1 terminating NULL byte The use-of-privilege token consists of: token ID 1 byte succ/fail 1 byte text length 2 bytes privilege used N bytes + 1 terminating NULL byte The command token consists of: token ID 1 byte count of args 2 bytes argument list (count times) text length 2 bytes argument text N bytes + 1 terminating NULL byte count of env strings 2 bytes environment list (count times) text length 2 bytes env. text N bytes + 1 terminating NULL byte The ACL token consists of: token ID 1 byte type 4 bytes value 4 bytes file mode 4 bytes The zonename token consists of: token ID 1 byte name length 2 bytes name <name length> including terminating NULL byte The label token consists of: token ID 1 byte label ID 1 byte compartment length 1 byte classification 2 bytes compartment words <compartment length> * 4 bytes The xatom token consists of: token ID 1 byte string length 2 bytes atom string string length bytes The xclient token consists of: token ID 1 byte client ID 4 bytes The xcolormap token consists of: token ID 1 byte XID 4 bytes creator UID 4 bytes The xcursor token consists of: token ID 1 byte XID 4 bytes creator UID 4 bytes The xfont token consists of: token ID 1 byte XID 4 bytes creator UID 4 bytes The xgc token consists of: token ID 1 byte XID 4 bytes creator UID 4 bytes The xpixmap token consists of: token ID 1 byte XID 4 bytes creator UID 4 bytes The xproperty token consists of: token ID 1 byte XID 4 bytes creator UID 4 bytes string length 2 bytes string string length bytes The xselect token consists of: token ID 1 byte property length 2 bytes property string property length bytes prop. type len. 2 bytes prop type prop. type len. bytes data length 2 bytes window data data length bytes The xwindow token consists of: token ID 1 byte XID 4 bytes creator UID 4 bytes AttributesSee attributes(5) for descriptions of the following attributes:
The binary file contents is Unstable. See Alsoaudit(1M), auditd(1M), bsmconv(1M), audit(2), auditon(2), au_to(3BSM), audit_control(4), audit_syslog(5) NotesEach token is generally written using the au_to(3BSM) family of function calls. Name | Synopsis | Description | Attributes | See Also | Notes |
|||||||||||||||||||||||||||||||||