Skip to contentSkip to conversation

ausearch notes

DISCUSSION LC Bruzenak 2 participants 2 messages May 30, 2008 – Jun 2, 2008

lore
Share & tools
lore
#0 lore raw

audit-1.7.4-1.fc9.x86_64

The "-i" flag on ausearch appears to remove the "node=" info when the type!=UNKNOWN:

[root@hugo sbin]# ausearch -ts today | grep -i welcome
...
node=hugo type=UNKNOWN[2800] msg=audit(1212175003.754:11074): user pid=20597 uid=0 auid=0 subj=root:staff_r:staff_t:s0-s15:c0.c1023 msg='*C* 5/30 19:16:43 comms 20836 audit test: Welcome to audit test LCB3 : exe="/opt/jcdx/sbin/SecureSyslog" (hostname=comms, addr=192.168.31.60, terminal=? res=failed)'
node=hugo type=TRUSTED_APP msg=audit(1212175342.808:11387): user pid=21612 uid=0 auid=0 subj=root:staff_r:staff_t:s0-s15:c0.c1023 msg='*C* 5/30 19:22:22 comms 21615 audit test: Welcome to audit test LCB3 : exe="/opt/jcdx/sbin/SecureSyslog" (hostname=comms, addr=192.168.31.60, terminal=? res=failed)'
...

[root@hugo sbin]# ausearch -i -ts today | grep -i welcome
...
node=hugo type=UNKNOWN[2800] msg=audit(05/30/2008 14:16:43.754:11074) :
user pid=20597 uid=root auid=root subj=root:staff_r:staff_t:s0-s15:c0.c1023 msg='*C* 5/30 19:16:43 comms 20836 audit test: Welcome to audit test LCB3 :
exe=/opt/jcdx/sbin/SecureSyslog (hostname=comms, addr=192.168.31.60, terminal=? res=failed)'
type=TRUSTED_APP msg=audit(05/30/2008 14:22:22.808:11387) : user pid=21612 uid=root auid=root subj=root:staff_r:staff_t:s0-s15:c0.c1023 msg='*C* 5/30 19:22:22 comms 21615 audit test: Welcome to audit test LCB3 : exe=/opt/jcdx/sbin/SecureSyslog (hostname=comms, addr=192.168.31.60, terminal=? res=failed)'
...

Signature · 2 lines
LC (Lenny) Bruzenak
[email protected]
#1 lore raw
Quoted 2 lines · On Friday 30 May 2008 17:12:25 LC Bruzenak wrote:

The "-i" flag on ausearch appears to remove the "node=" info when the type!=UNKNOWN:

Thanks for reporting this. It appears to be a long standing bug in that I don't think the code was ever put into place to do the right thing. I can see this in 1.6.5 and that's as far back as I checked. This will be fixed in the next release.

-Steve