Re: [RFC] Multibyte char handling

From: Date: Sat, 18 Jan 2014 13:41:54 +0000
Subject: Re: [RFC] Multibyte char handling
References: 1  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 
Yasuo Ohgaki wrote:

addslashes() could be vulnerable via char encoding based attacks.
It is needed to decide what counter measure we adopt.
This is RFC for this issue.

https://wiki.php.net/multibyte_char_handling

Please comment.


Multibyte characters are still a contentious area, and the current compromise of supporting multibyte content, but being essentially 'single byte' for the programming structure as been a solution adopted in a few projects. Firebird is once again debating the same point that they and PHP last discussed 10 years ago, and was too difficult so PHP6 floundered and Firebird remained essentially single byte strings in the metadata.

10 years on isn't it time to re-open the debate on making the core unicode since 32 bit processors are more likely to be the norm these days. Certainly if everything internal is UTF8, then all of the encoding problems are moved to the client interface?

(p.s rfc needs a little work via the spell checker and the link above is wrong)

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

Thread (31 messages)

« previous php.internals (#71244) next »