-
Notifications
You must be signed in to change notification settings - Fork 37.7k
tests: Add fuzzing harness for {Read,Write}{LE,BE}{16,32,64} (crypto/common.h) #19247
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
Conversation
9f523af
to
90ea479
Compare
Any thoughts on clarifying that |
90ea479
to
b429e0f
Compare
@MarcoFalke Good idea. Added! |
…taProvider& fuzzed_data_provider, const size_t length)
b429e0f
to
cf5b8f6
Compare
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
ACK cf5b8f6 |
…common.h) Summary: Backport of core [[bitcoin/bitcoin#19247 | PR19247]]. Test Plan: ninja bitcoin-fuzzers ./src/test/fuzz/crypto_common <path_to_corpus> Reviewers: #bitcoin_abc, PiRK Reviewed By: #bitcoin_abc, PiRK Differential Revision: https://reviews.bitcoinabc.org/D9117
backport: bitcoin#18867, bitcoin#19247, bitcoin#19222, bitcoin#18363, bitcoin#18190, bitcoin#18393, partial bitcoin#18047, bitcoin#18314, bitcoin#19143 (fuzzing harness backports: part 3)
Add fuzzing harness for
{Read,Write}{LE,BE}{16,32,64}
(crypto/common.h
).See
doc/fuzzing.md
for information on how to fuzz Bitcoin Core. Don't forget to contribute any coverage increasing inputs you find to the Bitcoin Core fuzzing corpus repo.Happy fuzzing :)