From: Eric Paris <eparis@redhat.com>
To: Matt Rixon <rixon@ltceng.com>
Cc: Linux-audit@redhat.com
Subject: Re: Benefit of 'arch' parameter for syscall rules
Date: Mon, 27 Sep 2010 13:10:40 -0400 [thread overview]
Message-ID: <1285607440.2815.39.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimPovSxON1DnpMkPL6FEKOHAgSwmdLuLsCrz_s=@mail.gmail.com>
On Mon, 2010-09-27 at 10:59 -0400, Matt Rixon wrote:
> Hi everyone,
> What is the benefit of using the 'arch' field parameter in a syscall
> rule? Is it necessary?
Yes, for some 'not so nice' (IMHO) reasons. The syscall name you give
to -S is translated to a number and then matched exactly. since syscall
#100 on x86_64 might not be the same as syscall #100 on x86_32 if you
don't supply a -F arch= you might end up getting chmod on 32bit and
socket on 64bit (I'm just making that up as an example)
I personally think userspace should handle that for you (instead of just
complaining lightly) if you don't enter -F arch= on a biarch system.
-Eric
prev parent reply other threads:[~2010-09-27 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 14:59 Benefit of 'arch' parameter for syscall rules Matt Rixon
2010-09-27 17:10 ` Eric Paris [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=1285607440.2815.39.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=Linux-audit@redhat.com \
--cc=rixon@ltceng.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