Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: some questions about Linux audit
Date: Thu, 08 Jun 2017 22:23:26 -0400	[thread overview]
Message-ID: <3428865.HnteqFykjv@x2> (raw)
In-Reply-To: <tencent_0193D9237412B4950085D37F@qq.com>

Hello,

On Thursday, June 8, 2017 9:46:48 PM EDT 358123097 wrote:
> Dear Sir/Madam,
> 
> Hello, I‘am a Chinese student, now I studying Linux audit and having some
> problems. I want to collect some information from network,such as the
> accessor’s IP and port. I defined a audit rule in machine A as follow, then
> I used “ping” and “vsftpd” programs to test audit. For example, I run "ping
> A" in another machine, I can't collect any information in A's audit log. In
> addition, I run "ssh A" , then I get some incomprehensible records that
> display in the picture below(eg saddr=inet6 host:::1 serv:45983 and
> saddr=inet6 host:::ffff:127.0.0.1 serv:41573).
> -a always,exit -F arch=b64 -S connect -S getsockname -S getpeername 

I am not sure of your intent (inbound vs outbound info). If you want to 
collect inbound information, you need to monitor syscalls for inbound events 
such as accept, accept4, recv, recvfrom. Ping uses ICMP packets and is not 
likely to show up in normal syscalls. You might find them by placing audit 
rules in the iptables rules.

-Steve

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

      reply	other threads:[~2017-06-09  2:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  1:46 some questions about Linux audit =?gb18030?B?MzU4MTIzMDk3?=
2017-06-09  2:23 ` 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=3428865.HnteqFykjv@x2 \
    --to=sgrubb@redhat.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