From: Doug Ewell (email@example.com)
Date: Mon Dec 28 2009 - 22:19:46 CST
Peter Krefting <peter at opera dot com> wrote:
>> UTF-32 is stateful/poses a security risk?
> If mistakenly interpreted as UTF-16 by a web browser that does not
> support UTF-32, it would introduce nul characters into the character
> stream, which may cause interesting problems.
Creating standards that forbid conformant browsers to support certain
encodings, discourage them from supporting others, and require them to
interpret others as if they were something else, doesn't exactly seem
like a constructive way to avoid problems like this.
-- Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org RFC 5645, 4645, UTN #14 | ietf-languages @ http://is.gd/2kf0s
This archive was generated by hypermail 2.1.5 : Mon Dec 28 2009 - 22:21:41 CST