From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, darryl.dixon@winterhouseconsulting.com
Subject: Re: Decoding arguments passed to system calls
Date: Wed, 4 Jul 2007 10:29:32 -0400 [thread overview]
Message-ID: <200707041029.32765.sgrubb@redhat.com> (raw)
In-Reply-To: <42015.65.99.233.211.1183416503.squirrel@pythonhacker.is-a-geek.net>
On Monday 02 July 2007 06:48:23 pm Darryl Dixon - Winterhouse Consulting
wrote:
> What you say about not being able to audit 'write()' is worrying to me. The
> problem with auditing write by inference from open(), is that one doesn't
> know *when* the file was written,
But you know who did it and when they started the process of writing to the
file by opening with the intent to write. mmap is not covered by auditing for
write, so you have a big hole anyways.
> My assumption would have been that CWD reflected only where the exe was
> launched from, and not necessarily where the write()-en file was located...
CWD is the processes' cwd. Some programs do a chdir("/") right after starting,
so CWD would reflect wherever the app chdir'ed to.
-Steve
next prev parent reply other threads:[~2007-07-04 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 21:46 Decoding arguments passed to system calls Darryl Dixon - Winterhouse Consulting
2007-07-02 22:27 ` Matthew Booth
2007-07-02 22:48 ` Darryl Dixon - Winterhouse Consulting
2007-07-02 23:23 ` Matthew Booth
2007-07-03 11:57 ` Stephen Smalley
2007-07-03 14:38 ` Stephen Smalley
2007-07-04 15:03 ` Steve Grubb
2007-07-03 13:04 ` Wieprecht, Karen M.
2007-07-04 14:29 ` Steve Grubb [this message]
2007-07-04 14:23 ` 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=200707041029.32765.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=darryl.dixon@winterhouseconsulting.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;
as well as URLs for NNTP newsgroup(s).