Docker/runner #7
Merged
Conversation
This file contains 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
|
It would be helpful if you can insert another section in the README to explain the usage |
|
Thanks for the new feature. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Features:
SyzScopeto expose a reproducible build for end-users.Hi, I've added a
Dockerfileto expose a reproducible build for researchers looking to reproduce the research.I'm aware that there are already docker images on dockerhub but I was interested in identifying the minimum system dependencies and permissions and being able to make changes if needed.
I've tested building and running
SyzScopeusing this docker build on my host running Ubuntu 20.04 LTS and Docker version 20.10.17.There's a small quirk that I'm going to push a fix for related to the
syzkallerbuild at run-time. Additionally, despite the kernel build running to completion, my target kernel would immediately exit in QEMU.However by copying over the
bzImageandvmlinuxfiles from theetenal/syzscope:ready2gocontainer image, I was able to reproduce the CVE-2018-25015 example by running the commandpython3 syzscope -i a8d38d1b68ffc744c53bd9b9fc1dbd6c86b1afe2 -RP -SE --timeout-symbolic-execution 3600.Currently, the build aligns more with the
etenal/syzscope:minicontainer image. For some reason, runningrequirements.shin the docker build isn't persisting the changes in order to have a build that aligns with theetenal/syzscope:ready2gocontainer image.