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