From c2b1f1137e757b3a3f21e7c6dda333b058e84e85 Mon Sep 17 00:00:00 2001 From: Sean Donner Date: Wed, 13 Feb 2013 18:40:58 -0500 Subject: system/sudosh2: Added (tool for server auditing and shell reporting) Signed-off-by: dsomero --- system/sudosh2/README | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 system/sudosh2/README (limited to 'system/sudosh2/README') diff --git a/system/sudosh2/README b/system/sudosh2/README new file mode 100644 index 0000000000..cb5fa47a86 --- /dev/null +++ b/system/sudosh2/README @@ -0,0 +1,20 @@ +sudosh is a filter and can be used as a login shell. sudosh takes advantage +of pty devices in order to sit between the user's keyboard and a program, in +this case a shell. + +sudosh was designed specifically to be used in conjunction with sudo or by +itself as a login shell.. sudosh allows the execution of a root shell with +logging. Every command the user types within the root shell is logged as +well as the output. + +How is this different than "sudo -s" or "sudo /bin/sh" ? + +Using "sudo -s" or other methods doesn't log commands typed to syslog. +Generally the commands are logged to a file such as .sh_history and if you +use a shell such as csh that doesn't support command-line logging you're +out of luck. + +sudosh fills this gap. No matter what shell you use, all of the command +lines are logged to syslog (including vi keystrokes.) + +See README in /usr/doc/sudosh2- for configuration and usage. -- cgit v1.2.3