From: Max Williams <Max.Williams@betfair.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: RE: Auditing the "chattr" command (ioctl syscall?)
Date: Wed, 24 Aug 2011 16:04:39 +0000 [thread overview]
Message-ID: <D0A5F96279337C499E18E7D5B0695A2F67DD6A0C@HAMMBX02.uk.betfair.local> (raw)
In-Reply-To: <201108241153.15707.sgrubb@redhat.com>
Ah, the 0x was it! It was producing the wrong rule:
Wrong: LIST_RULES: exit,always arch=3221225534 (0xc000003e) a1=40086602 (0x263ac4a) key=chattr1 syscall=ioctl
Right: LIST_RULES: exit,always arch=3221225534 (0xc000003e) a1=1074292226 (0x40086602) key=chattr3 syscall=ioctl
You are right, if I specify a path for this rule, it stops working.
Thank you very much for your help Steve.
Cheers,
Max
-----Original Message-----
From: linux-audit-bounces@redhat.com [mailto:linux-audit-bounces@redhat.com] On Behalf Of Steve Grubb
Sent: 24 August 2011 16:53
To: linux-audit@redhat.com
Subject: Re: Auditing the "chattr" command (ioctl syscall?)
On Wednesday, August 24, 2011 10:40:32 AM Steve Grubb wrote:
> So, the rule is:
>
> -a always,exit -F arch=b64 -S ioctl -F a1=40086602
One correction, you need a 0x in that:
-a always,exit -F arch=b64 -S ioctl -F a1=0x40086602
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
________________________________________________________________________
In order to protect our email recipients, Betfair Group use SkyScan from
MessageLabs to scan all Incoming and Outgoing mail for viruses.
________________________________________________________________________
prev parent reply other threads:[~2011-08-24 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 13:57 Auditing the "chattr" command (ioctl syscall?) Max Williams
2011-08-24 14:40 ` Steve Grubb
2011-08-24 15:31 ` Max Williams
2011-08-24 15:50 ` Steve Grubb
2011-08-24 15:53 ` Steve Grubb
2011-08-24 16:04 ` Max Williams [this message]
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=D0A5F96279337C499E18E7D5B0695A2F67DD6A0C@HAMMBX02.uk.betfair.local \
--to=max.williams@betfair.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.