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 converting fuzz tests to LibAFL #610

Open
ordian opened this issue Jan 4, 2022 · 2 comments
Open

Consider converting fuzz tests to LibAFL #610

ordian opened this issue Jan 4, 2022 · 2 comments
Labels
F6-refactor good-first-issue Good first issue for external contributors Q2-easy

Comments

@ordian
Copy link
Member

ordian commented Jan 4, 2022

It already outperforms many well-known coverage-guided fuzzers in Google's fuzzbench1 benchmark, including honggfuzz, libfuzzer/entropic, as well as old-skool afl. On top, LibAFL2 scales better across cores and machines.

Footnotes

  1. https://www.fuzzbench.com/reports/experimental/2021-12-15-libafl/index.html ↩

  2. https://github.com/AFLplusplus/LibAFL ↩
@ordian ordian added Q2-easy F6-refactor good-first-issue Good first issue for external contributors labels Jan 4, 2022
@ordian
Copy link
Member Author

ordian commented Feb 18, 2022

https://github.com/camshaft/bolero also looks interesting as a unification interface across fuzz engines.

@Polkadot-Forum
Copy link

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/testing-complex-frame-pallets-discussion-tools/356/4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
F6-refactor good-first-issue Good first issue for external contributors Q2-easy
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ordian @Polkadot-Forum