-
Notifications
You must be signed in to change notification settings - Fork 15
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
TODO: fuzzing #11
Comments
Hi, |
yeah, however we do not bother with creation of .po files, we just make .mo files from it.
that's basically it. :) |
@xhebox : do you know off the top of your head a package that ships .po files which use rarely used features like fuzzy marks and msg-ctx ? |
@rofl0r the instructions were very helpful. See https://github.com/rwhitworth/gettext-tiny-fuzz Valgrind output from a few of the inputs (not exhaustive):
|
cool, thanks a lot! will you keep the repo with the crash-testcases on your profile for a while? |
Yeah, they'll be up for at least a month. Eventually I'll consolidate all my fuzzing repos to keep my repo list clean, but it'll be a while. Let me know if I can be of further assistance. I'll be glad to test again after changes are made to help verify. |
@rofl0r from krita, the most complex and biggest single translation file i guess.
So, we got segfault examples in gettext-tiny-fuzz? I'll look in to them this week.. :) |
as now gettext-tiny supports quite a lot or almost all features of .po files, we should run some stress-tests with afl-fuzz, paired with asan so out-of-bounds reads get caught. better we do that before a release so no CVEs get filed :)
The text was updated successfully, but these errors were encountered: