-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[poppler] Add poppler #1431
[poppler] Add poppler #1431
Conversation
I don't think aacid@kde.org has an associated google account you can use tsdgeos@gmail.com i guess |
This is ready to merge. |
projects/poppler/pdf_fuzzer.options
Outdated
@@ -0,0 +1 @@ | |||
[libfuzzer] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
So i just realized the test code is wrong and is not checking for is_locked before trying to use the document which is basically a misuse of the API (that ends up in crashes if you do, but that's not a security issue, it's just people not using the library correctly) I guess i should just propose a fix? |
* [poppler] Add poppler * cleanup * remove empty options
As requested in #402.
👋 @tsdgeos This adds a fuzzer for poppler that will be continuously updated and run in the OSS-Fuzz infrastructure. Assuming you are okay with this, please confirm that
aacid@kde.org
is your email address and has a Google account associated with it (this account will be used to access restricted bugs filed by the fuzzers). Also, should anyone else have access to the bugs?