On Thu, 5 Aug 2010 10:20:12 +0900 Jordi Beltran Creix <[email protected]> wrote:
> 2010/8/5 Matthew Dempsky <[email protected]>: > > On Wed, Aug 4, 2010 at 6:22 AM, Jordi Beltran Creix > > All programs that output raw strings, don't attempt alignment, and > don't work with glyphs or code points(stuff like regexes is out but > not simple matching and replacement), are safe from i18n. If you > ignore its features, UTF-8 is just like ASCII and nothing has to > change, no need to use Unicode functions for everything. Reminded me of the php escapeshellarg exploit that only worked on utf-8 enabled systems, if you didn't do your own filtering that is. Is there anything like that in perl or anywhere else that may need considering? I guess most/if not all code where it would be a problem, would be made for utf-8 systems anyway.
