From: Steve Grubb <sgrubb@redhat.com>
To: paul moore <paulmoore100@hotmail.com>
Cc: linux-audit@redhat.com
Subject: Re: hexified path in cwd audit message if dir no longer exists
Date: Mon, 7 May 2007 13:49:22 -0400 [thread overview]
Message-ID: <200705071349.22847.sgrubb@redhat.com> (raw)
In-Reply-To: <BAY106-DAV109418B867C7B6446054818C450@phx.gbl>
On Monday 07 May 2007 13:42, paul moore wrote:
> Aha - it actually says "xxxx (deleted)".
That's what I thought it would say.
> Which is OK I guess. But I would have thought that the unstrusted string
> routine would know that this is a string generated by the kernel audit
> system and so not escape it
Any space in a field value will cause parsing problems. That is the main
reason its escaped.
-Steve
prev parent reply other threads:[~2007-05-07 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000301c78eae$ef9128f0$656fa8c0@centrify.com>
2007-05-05 0:47 ` hexified path in cwd audit message if dir no longer exists paul moore
2007-05-05 13:33 ` Steve Grubb
[not found] ` <000001c790c7$82439fb0$656fa8c0@centrify.com>
2007-05-07 16:48 ` paul moore
[not found] ` <000101c790cf$200dbdf0$656fa8c0@centrify.com>
2007-05-07 17:42 ` paul moore
2007-05-07 17:49 ` 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=200705071349.22847.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paulmoore100@hotmail.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