Gentoo Archives: gentoo-server

From: Joey McCoy <ixion@××××××.com>
To: gentoo-server@l.g.o
Cc: gentoo-server@l.g.o
Subject: Re: [gentoo-server] Root commands > syslog
Date: Thu, 17 Jun 2004 19:46:28
Message-Id: 61188.24.227.114.194.1087501410.squirrel@24.227.114.194
In Reply to: Re: [gentoo-server] Root commands > syslog by "Rev. Jeffrey Paul"
1 I agree, the GRSec Kernel Auditing features work quite well and are just
2 informative enough to give you the info you're looking for... :)
3
4 > On Thu, Jun 17, 2004 at 09:47:25AM -0700, Jason Qualkenbush wrote:
5 >>
6 >> As far as logging commands once someone gets a root shell, I did find
7 >> some info (if anyone is interested). First, there was syscalltrack
8 >> (http://syscalltrack.sourceforge.net/index.html) which seems to work,
9 >> but looks to be more like a debugging tool.
10 >>
11 >> I did find a bash shell patch called bash-bofh that logs all commands to
12 >> syslog. Though, I the only pages I seem to find are hacker oriented
13 >> pages and the homepage seems to raise backdoor questions
14 >> (http://www.ccitt5.net). Still, the bash-bofh is the closest to what I
15 >> seek so far.
16 >
17 > These methods, as well as the sudo one mentioned earlier in this thread,
18 > are all unreliable.
19 >
20 > I assume most of you are already using the gentoo kernel or have
21 > grsecurity patched into whatever other kernel you're using on your
22 > servers; simply turn on exec and chdir logging.
23 >
24 > Example:
25 > Jun 17 15:27:46 [kernel] grsec: exec of [03:03:207557] (tail current ) by
26 > (bash:12670) UID(0) EUID(0), parent (bash:30029) UID(0) EUID(0)
27 >
28 > -j
29 >
30 > --
31 > --------------------------------------------------------
32 > Rev. Jeffrey Paul -datavibe- sneak@××××××××.net
33 > aim:x736e65616b pgp:0x15FA257E phone:8777483467
34 > 70E0 B896 D5F3 8BF4 4BEE 2CCF EF2F BA28 15FA 257E
35 > --------------------------------------------------------
36 >
37
38
39 --

Replies

Subject Author
Re: [gentoo-server] Root commands > syslog Joey Abaya Panoy <japanoy@×××××××××××.com>