linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Eric Howard" <pt3vjld02@sneakemail.com>
To: linux-audit@redhat.com
Subject: Not trapping 'symlink' system call
Date: 6 Jun 2007 19:56:49 -0000	[thread overview]
Message-ID: <13697-64304@sneakemail.com> (raw)

Ah, I see my mistake.  I was using 'possible' instead of 'always'.  Thanks for your help!

-- Eric --

Steve Grubb sgrubb-at-redhat.com |redhat-audit-mailing-list| wrote:
> On Wednesday 06 June 2007 14:40, Eric Howard wrote:
>> I have been tasked to generate test cases to validate the proper execution
>> of particular syscall audit flags.
> 
> I think HP open sourced a test suite that tests the audit system:
> http://sourceforge.net/projects/audit-test
> 
>> In most cases I have succeeded in triggering audit log entries.  However, I
>> have been unable to trigger audit entries for the 'symlink call'  My test
>> cases are generated by a shell script that execute commands to trigger the
>> relevant calls.  In my test case I created a hard-link and a soft-link
>> using /bin/ln.  Running strace indicated that the syscall was definitely
>> made but  'ausearch -sc symlink' shows nothing.  I am using
>> audit-1.0.15-3.EL4.  Any insight into this problem would be appreciated.
> 
> Looking at the syscalls, it should trigger on something like:
> 
> auditctl -a always,exit -S symlink
> 
> Or were you testing it another way?
> 
> -Steve
> 




--------------------------------------
Protect yourself from spam, 
use http://sneakemail.com

             reply	other threads:[~2007-06-06 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 19:56 Eric Howard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-06 18:40 Not trapping 'symlink' system call Eric Howard
2007-06-06 19:25 ` Steve Grubb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13697-64304@sneakemail.com \
    --to=pt3vjld02@sneakemail.com \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).