From: John Dennis <jdennis@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: A change to string encoding
Date: Tue, 10 Mar 2009 15:55:44 -0400 [thread overview]
Message-ID: <49B6C5C0.9000204@redhat.com> (raw)
In-Reply-To: <200903101158.38990.sgrubb@redhat.com>
Steve Grubb wrote:
> Can you encode data structures in it? The kernel developer at the time wanted
> something that was either already in the kernel or something that could be
> implemented in a couple lines of code and something that works for any kind
> of encoding that needed to be done. So, I think minimal amount of code and
> maximum flexibility is what drove the decision.
>
The comment was *not* about encoding data structures, rather it was
about string encoding.
I have provided code in the past which encodes a string according to the
ISO C99 standard. It does not tax the kernel, use excessive resources,
or is complicated in any sense whatsoever (it's just a per character
table lookup) and wraps the result in double quotes.
Yes, this would change the output of the kernel audit data, which does
have the potential to break existing user code. However, it's often been
stated only the official audit libraries should ever be used to read
audit data and if that recommendation still holds then the audit
libraries should be capable of gracefully handling either the old or new
format providing a transparent transition.
I hope at some point we can start to address this reoccurring issue.
--
John Dennis <jdennis@redhat.com>
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
next prev parent reply other threads:[~2009-03-10 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 11:07 A change to string encoding Matthew Booth
2009-03-10 15:58 ` Steve Grubb
2009-03-10 18:13 ` Matthew Booth
2009-03-10 19:55 ` John Dennis [this message]
2009-03-10 16:22 ` Tomas Mraz
2009-03-10 18:51 ` Eric Paris
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=49B6C5C0.9000204@redhat.com \
--to=jdennis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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