All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Miloslav Trmac <mitr@redhat.com>, Alexander <goal81@gmail.com>
Subject: Re: Regarding bug 435682
Date: Fri, 21 Oct 2011 08:58:24 -0400	[thread overview]
Message-ID: <201110210858.24462.sgrubb@redhat.com> (raw)
In-Reply-To: <6962cb6b-c2c2-406c-87c5-e7ed306dd840@zmail07.collab.prod.int.phx2.redhat.com>

On Friday, October 21, 2011 08:49:30 AM Miloslav Trmac wrote:
> > Here's a patch for version 2.1.3 which solves bug 435682 (
> > https://bugzilla.redhat.com/show_bug.cgi?id=435682 ).
> > Patched auditctl allows to specify files having spaces in ther names
> > - just surround a filename with apostrophes.
> 
> This patch also arbitrarily breaks handling of apostrophes and \xFF
> characters in filenames; it probably is a marginal improvement, but any
> change to the format should IMHO start with an explicit and consistent
> specification of how quoting is supposed to work in audit.rules, and then
> implementing exactly that.
>
> If we do have to change the file format to support spaces, let's do it, but
> let's also make sure that we don't need to change it again soon to fix
> different artifacts of the parser implementation. Mirek

I was thinking of using the same mechanism as shell escaping '\' since this is how 
bash would present the path to the user.

-Steve

  reply	other threads:[~2011-10-21 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 14:48 Regarding bug 435682 Alexander
2011-10-21 12:49 ` Miloslav Trmac
2011-10-21 12:58   ` Steve Grubb [this message]
2011-10-21 13:03   ` Alexander
  -- strict thread matches above, loose matches on Subject: below --
2011-10-28 13:56 Alexander
2011-12-03 13:44 ` 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=201110210858.24462.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=goal81@gmail.com \
    --cc=linux-audit@redhat.com \
    --cc=mitr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.