FIT: add seeds for fuzzing fitimage signing #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To test the fitimage signing codepath a fitimage with a signing key is
needed as input. The file sandbox.its describes this fitimage, which
than can be generated with mkimage.
Three different iterations from this input are generated:
fit/fit-image-null.bin
fit/fit-image-only-dtb.bin
fit/fit-image-sign.bin
These represent a fitimage with no data for kernel and dtb, only a dtb
and with a dtb and a signing key. These inputs result in different code
paths in the fitimage parser.
The binary seeds that are generated from these inputs by the fuzzer are
also added.
Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Member
|
Thanks @strumtrar, can you also include the dtsi snippet that needs to be passed to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To test the fitimage signing codepath a fitimage with a signing key is needed as input. The file sandbox.its describes this fitimage, which than can be generated with mkimage.
Three different iterations from this input are generated:
fit/fit-image-null.bin
fit/fit-image-only-dtb.bin
fit/fit-image-sign.bin
These represent a fitimage with no data for kernel and dtb, only a dtb and with a dtb and a signing key. These inputs result in different code paths in the fitimage parser.
The binary seeds that are generated from these inputs by the fuzzer are also added.