From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: hsultan@thefroid.net
Subject: Re: listen & accept sycalls not present in b32 ?
Date: Thu, 15 Jan 2015 12:15 -0500 [thread overview]
Message-ID: <5435909.YIfZJDsvq9@x2> (raw)
In-Reply-To: <898451c9c5da703102eaec8c33f98693@thefroid.net>
On Tuesday, January 13, 2015 12:13:16 PM hsultan@thefroid.net wrote:
> sudo auditctl -a exit,always -F arch=b32 -S listen -S connect
> Syscall name unknown: listen
>
> however with b64 it works
>
> Same with the accept syscall.
>
> Is that expected ? How can I grab the 32bit calls then ?
This is expected. The 32 bit ABI for x86 is very old. For whatever reason,
they decided that dedicating a syscall to each networking call was
unreasonable and its all done through the socketcall(2) system call. To audit
those calls, you would have to look up the define for each one
include/linux/net.h
and use that number for arg0.
-Steve
prev parent reply other threads:[~2015-01-15 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 20:13 listen & accept sycalls not present in b32 ? hsultan
2015-01-15 17:15 ` Steve Grubb [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=5435909.YIfZJDsvq9@x2 \
--to=sgrubb@redhat.com \
--cc=hsultan@thefroid.net \
--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