You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I saw the recent changes to the UTF-8 parsing (on HN) and while speed is always appreciated, there is a whole class of bugs related to bad parsing of UTF-8 strings (https://en.m.wikipedia.org/wiki/UTF-8#Invalid_sequences_and_error_handling, http://www.unicode.org/reports/tr36/#Canonical_Represenation). Given that, I am thinking that code path should be fuzzed/tested a lot more to make sure the clever tricks correctly handle intentionally malformed input. I am happy to contribute some tests, just opening the issue to get some feedback.
Thanks
The text was updated successfully, but these errors were encountered:
Hi!
I saw the recent changes to the UTF-8 parsing (on HN) and while speed is always appreciated, there is a whole class of bugs related to bad parsing of UTF-8 strings (https://en.m.wikipedia.org/wiki/UTF-8#Invalid_sequences_and_error_handling, http://www.unicode.org/reports/tr36/#Canonical_Represenation). Given that, I am thinking that code path should be fuzzed/tested a lot more to make sure the clever tricks correctly handle intentionally malformed input. I am happy to contribute some tests, just opening the issue to get some feedback.
Thanks
The text was updated successfully, but these errors were encountered: