News for hackers. Stuff that matters.

A comment on UTF-8 history (2003). Parent comment

Re:UTF-8 history (2003) by mirekrusin on Thursday October 10, 2019 @06:23AM (#21212772)
You can also construct malicious payloads which will DoS many implementations with architecture like that.
[ Parent | on HN ]
Re:UTF-8 history (2003) by kstenerud on Thursday October 10, 2019 @06:30AM (#21212810)
You can also trivially defend against that by having a max travel distance of, say, 4.
[ Parent | on HN ]
Re:UTF-8 history (2003) by mirekrusin on Saturday October 12, 2019 @09:41PM (#21237700)
Exactly, so you arrived at the same conclusion - fixed distance so you can safely pick up stream at arbitrary position.
[ Parent | on HN ]
Re:UTF-8 history (2003) by kstenerud on Sunday October 13, 2019 @08:38AM (#21240061)
The difference is that the distance limits would be inherent to the codec itself, rather than taking up extra space in the data stream.
[ Parent | on HN ]
Re:UTF-8 history (2003) by ludamad on Thursday October 10, 2019 @04:55PM (#21219078)
Is that guaranteed to catch all valid cases?
[ Parent | on HN ]