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.

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

Update Fuzzer documentation and Configuration #4114

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Logix64
Copy link

@Logix64 Logix64 commented Jun 11, 2024

This references #4061. With these changes both ASL and libFuzzer build on my device. Extending on that, I would like to continue to update the fuzzing source code, but I don't know how exactly (especially the RNG part).

Any help would be appreciated.

@randombit randombit self-requested a review June 11, 2024 21:27
@coveralls
Copy link

Coverage Status

coverage: 91.769% (+0.003%) from 91.766%
when pulling 7449189 on Logix64:update-fuzzing
into 856174e on randombit:master.

@coveralls
Copy link

Coverage Status

coverage: 91.773% (+0.007%) from 91.766%
when pulling 5b0cd25 on Logix64:update-fuzzing
into 856174e on randombit:master.

Copy link
Owner

@randombit randombit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Logix64 thanks so much for taking this on! This is definitely a nice improvement especially the span bit. There are a couple trivial warnings from clang-tidy and some formatting things (there is a diff in the format CI job) that need to be addressed. For the RNG part I'll give more context in the original ticket.

std::make_shared<Botan::ChaCha_RNG>(Botan::secure_vector<uint8_t>(32));
inline std::shared_ptr<Botan::System_RNG> fuzzer_rng_as_shared() {
static std::shared_ptr<Botan::System_RNG> rng =
std::make_shared<Botan::System_RNG>();
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This definitely doesn't work - the non-determinism of the RNG will confuse the fuzzer. Lets revert this bit and then take up the RNG piece in a future PR. I'll add more context in the original ticket

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, thank you. I changed it in my recent commit.

@Logix64 Logix64 marked this pull request as ready for review June 17, 2024 12:17
@coveralls
Copy link

Coverage Status

coverage: 91.766%. remained the same
when pulling b89a10c on Logix64:update-fuzzing
into 856174e on randombit:master.

@randombit
Copy link
Owner

Thanks @Logix64 this is a nice cleanup. Can you rebase then squash the last 3 commits? Other than that this looks to me ready to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants