public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: "Bob Kryger" <bobk@sac.com>
To: linux-audit@redhat.com
Subject: auditing nfs
Date: Tue, 26 Feb 2008 16:54:13 -0500	[thread overview]
Message-ID: <47C48A85.20508@sac.com> (raw)

So, I'm looking to audit file access (via syscalls 
create,open,unlink,etc. because I want every file in the filesystem and 
do not want to have to specify an audit rule for each dir/file) that are 
accessed via nfs from the nfs server. It seems, I assume because nfs is 
in the kernel, that I am not getting any audit messages for those nfs 
files access.

Is my assumption correct?
Any suggestions for auditing from the nfs server side?

BTW: not a list subscriber, please reply directly.

Thanks
Bob

-- 
Bob Kryger                                        Office: 212-813-8677
Systems/Network Administrator                       Cell: 917-913-6670
SAC Capital, Synapse Group                         email: bobk@sac.com
540 Madison Ave                                      AIM: sacbobk
New York, NY 10022


DISCLAIMER: This e-mail message and any attachments are intended solely for the use of the individual or entity to which it is addressed and may contain information that is confidential or legally privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and permanently delete this message and any attachments. 

             reply	other threads:[~2008-02-26 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 21:54 Bob Kryger [this message]
2008-03-03 21:09 ` auditing nfs Steve Grubb

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=47C48A85.20508@sac.com \
    --to=bobk@sac.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