From: Valdis.Kletnieks@vt.edu
To: Matthew Booth <mbooth@redhat.com>
Cc: linux-audit <linux-audit@redhat.com>
Subject: Re: Format of EXECVE
Date: Mon, 17 Sep 2007 16:54:13 -0400 [thread overview]
Message-ID: <17971.1190062453@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 17 Sep 2007 17:50:16 BST." <1190047816.14088.17.camel@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 558 bytes --]
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).
[-- Attachment #1.2: Type: application/pgp-signature, Size: 226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-09-17 20:54 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 [this message]
2007-09-17 21:31 ` Matthew Booth
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=17971.1190062453@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-audit@redhat.com \
--cc=mbooth@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