-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define a IsValidUtf8
equivalent with unit tests
#30386
Conversation
PR #30386: Size comparison from f50e12b to 967c32b Full report (8 builds for cc32xx, mbed, nrfconnect, qpg)
|
PR #30386: Size comparison from f50e12b to 6e2f7d3 Full report (2 builds for cc32xx)
|
PR #30386: Size comparison from f50e12b to 69135af Full report (73 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
Spec reference from Boris, btw. A.11.2. UTF-8 and Octet Strings. https://github.com/CHIP-Specifications/chip-test-plans/issues/3680 |
I may cover that out of the box once I add this to our TLV bits. I was planning to:
|
provide a
chip::Utf8::IsValid
implementationIt seems we want to start have some encoding validations, at least outgoing (and maybe inside the cert) so that bugs like #30342 are not possible.
Having UTF8 validation seems very beneficial.