From: Matt Anderson <mra@hp.com>
To: "Upadhyay, Vikas" <Vikas.Upadhyay@in.unisys.com>, linux-audit@redhat.com
Subject: Re: porting test suite ( testing audit system ) from RHEL 3 to RHEL 4
Date: Tue, 23 May 2006 11:57:11 -0400 [thread overview]
Message-ID: <447330D7.3050508@hp.com> (raw)
In-Reply-To: <88299102B8C1F54BB5C8E47F30B2FBE202CCB051@inblr-exch1.eu.uis.unisys.com>
Upadhyay, Vikas wrote:
> I want to port the LTP test suite, linux_security_test_suite_EAL3.tar.gz
> (available from http://ltp.sourceforge.net/EAL3.RHEL.html) from RHEL 3
> to RHEL 4. The major issue is porting of *laus_test* directory, which
> tests the underlying audit system and the audit system has undergone a
> substantial change from RHEL 3 to RHEL 4.
>
> I plan to change the directory *laus_test*, which tests *LAuS* on *RHEL
> 3* to something like, *audit_test*, which will test the current audit
> system (on *RHEL 4*). And for that, I need to change each and every
> single file in the directory *laus_test*. I am unable to find any
> detailed document on the new audit system.
>
> Any pointers will be really appreciated.
You probably want to check out our audit-test package. We recently got
it added to sourceforge: http://sourceforge.net/projects/audit-test
HP hasn't had much time to work on it as we're getting ready for the
next evaluation, but it will be a better starting point. Maybe if we
get some more people using it (and sending patches) we'll be able to
justify spending more time on it.
-matt
next prev parent reply other threads:[~2006-05-23 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 11:52 porting test suite ( testing audit system ) from RHEL 3 to RHEL 4 Upadhyay, Vikas
2006-05-23 15:57 ` Matt Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-24 7:11 Upadhyay, Vikas
2006-05-24 14:18 Upadhyay, Vikas
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=447330D7.3050508@hp.com \
--to=mra@hp.com \
--cc=Vikas.Upadhyay@in.unisys.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