Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Consider adopting fuzzing #6

Open
ghost opened this issue May 23, 2017 · 1 comment
Open

Consider adopting fuzzing #6

ghost opened this issue May 23, 2017 · 1 comment
Labels
enhancement

Comments

@ghost
Copy link

ghost commented May 23, 2017 •
edited by ghost
Loading

In the future, it might be good for ContentMine to start fuzzing its codebase. This would generate a more varied input than corpora do, and might help catch bugs that otherwise would not be caught, including potentially security issues.

LibreOffice - which, a bit like ContentMine, is designed to handle heterogeneous input files - has recently adopted fuzzing with some success: https://lwn.net/Articles/723566/
@ghost ghost added the enhancement label May 23, 2017
@petermr petermr closed this as completed Jun 15, 2017
@ghost
Copy link
Author

ghost commented Jun 15, 2017

Re-opening, as issue has not been resolved and seems to have been closed erroneously. (Cf. #5 (comment) .)

@ghost ghost reopened this Jun 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@petermr