From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [PATCH] Fix acct quoting in audit_log_acct_message()) Date: Wed, 5 Mar 2008 10:29:10 -0500 Message-ID: <200803051029.11017.sgrubb@redhat.com> References: <47CEA640.7090903@redhat.com> <47CEB674.8020104@redhat.com> <1204730489.12783.56.camel@vespa.frost.loc> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1204730489.12783.56.camel@vespa.frost.loc> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Wednesday 05 March 2008 10:21:29 Tomas Mraz wrote: > > Lets not invent YAES (Yet Another Encoding System). The world already > > has enough :-) There is value in sticking with known encodings, many > > programmers are instantly familiar with them and there is a raft of > > working code to support them. Off the top of my head I can think of: > > > > 1) backslash escapes with embedded octals > > 2) quoted printable > > 3) base64 > > 4) xml entities > > 5) url encoding - which is what I proposed and is most efficient and > readable (well it is equivalent to quoted printable except it uses % > instead of = which we cannot use as it has already a meaning as name > value separator) And if base64 is being suggested, why not: 6) ASCII encoded hex. Its compact, saves diskspace, easily encodes any utf-8 or ASCII string including punctuation and whitespace. -Steve