aboutsummaryrefslogtreecommitdiff
path: root/system/sudosh2/README
diff options
context:
space:
mode:
authorSean Donner <sean.donner@gmail.com>2013-02-13 18:40:58 -0500
committerdsomero <xgizzmo@slackbuilds.org>2013-02-13 19:34:06 -0500
commitc2b1f1137e757b3a3f21e7c6dda333b058e84e85 (patch)
treecff3695b6570089d0c45e179453f09888f584ed4 /system/sudosh2/README
parent73706918a5e0a4bb178a43f4a9d8e2f3855163a7 (diff)
system/sudosh2: Added (tool for server auditing and shell reporting)
Signed-off-by: dsomero <xgizzmo@slackbuilds.org>
Diffstat (limited to 'system/sudosh2/README')
-rw-r--r--system/sudosh2/README20
1 files changed, 20 insertions, 0 deletions
diff --git a/system/sudosh2/README b/system/sudosh2/README
new file mode 100644
index 0000000000000..cb5fa47a868e4
--- /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-<version> for configuration and usage.