From: Matthew Booth <mbooth@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-audit <linux-audit@redhat.com>
Subject: Re: Format of EXECVE
Date: Mon, 17 Sep 2007 22:31:17 +0100 [thread overview]
Message-ID: <1190064677.4993.27.camel@localhost.localdomain> (raw)
In-Reply-To: <17971.1190062453@turing-police.cc.vt.edu>
[-- Attachment #1.1: Type: text/plain, Size: 901 bytes --]
On Mon, 2007-09-17 at 16:54 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 17 Sep 2007 17:50:16 BST, Matthew Booth said:
>
> > I'm considering expanding argv[0] of EXECVE to be an absolute path.
>
> I take it you mean "*an* absolute path that was valid when we cut the EXECVE
> record", and document that it may not be *the* actual path used? In a quarter
> century, I've just seen *too* many race conditions, tricks with ../symlink/foo
> links, and the like (including some interesting malware that would dynamically
> create a symlink and execve through it, just to frustrate attempts at figuring
> out which binary was being exploited).
This would be an issue in a single-pronged approach.
Matt
--
Matthew Booth, RHCA, RHCSS
Red Hat, Global Professional Services
M: +44 (0)7977 267231
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2007-09-17 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 16:50 Format of EXECVE Matthew Booth
2007-09-17 18:07 ` Steve Grubb
2007-09-17 20:54 ` Valdis.Kletnieks
2007-09-17 21:31 ` Matthew Booth [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=1190064677.4993.27.camel@localhost.localdomain \
--to=mbooth@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--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