Since RHEL 5.4, and in recent Fedora releases, it’s possible to audit what users type at their tty (command prompt), thanks to the work of Steve Grubb, a RedHat employee.<\/p>\n
Edit \/etc\/pam.d\/system-auth and append the following, but not both<\/strong>:<\/p>\n Wait for users to log in and type into a terminal. Later, to see audited tty input, run:<\/p>\n When a user logs in, the pam module tells the kernel to enable tty auditing for a process and its children. All tty input is logged, but it may not be incredibly easy to read (it includes backspaces, control characters, etc.). I’m unclear as to when and how often the kernel flushes out accumulated tty input to the audit log. The records are identified with a type of TTY in \/var\/log\/audit\/audit.log.<\/p>\n In addition to tty auditing, RedHat patched their bash shell so that it neatly audits each and every command line it executes, with a record type of USER\\_TTY. It’s prettier to read than raw tty auditing — and it’s easy for a user to bypass by using a shell that doesn’t send its commands to the Linux audit system, like zsh, or a custom-built unpatched bash. Maybe that’s why “aureport –tty” doesn’t show USER\\_TTY records.<\/p>\n —-<\/p>\n The Linux auditing system is powerful. It’s possible to write rules that watch for modification to certain files, or that log the use of certain system calls. See the “audit.rules” manpage for more information.<\/p>\n","protected":false},"excerpt":{"rendered":" Since RHEL 5.4, and in recent Fedora releases, it’s possible to audit what users type at their tty (command prompt), thanks to the work of Steve Grubb, a RedHat employee. Edit \/etc\/pam.d\/system-auth and append the following, but not both: session required pam\\_tty\\_audit.so disable=\\* enable=root session required pam\\_tty\\_audit.so enable=\\* Wait for users to log in and … <\/p>\nsession required pam\\_tty\\_audit.so disable=\\* enable=root\r\nsession required pam\\_tty\\_audit.so enable=\\*<\/pre>\n
aureport --tty<\/pre>\n