You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like docker build should be started as root, otherwise i receive error, that docker can't connect to docker daemon socket.
Also docker build requires path to directory that holds Dockerfile.
If that's correct, i suppose README.md needs to be updated accordingly.
Q2
I also noticed, that 32-bit libraries failed to build in docker container. Furthermore, in that case we're not able to quickly fix it by installing some additional packages and running make again, as AFLplusplus directory gets deleted at the end of docker build process. :(
Q3
I have built my image, and then i start container with this command:
# docker run -it --name afl --rm aflplusplus
There are afl-* binaries present with libraries like libdislocator.
How to use them? Should i somehow transfer sources of my tested projects to the container? In that case what about my billions of RHEL SourceRPM legacy dependencies?
Or should i take AFL binaries from container to my system? Neither of that?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
well the README is for people who know and use docker :) so your Q1 is rather obvious for those people ;) but I will update the readme for Q1.
Q2 - same. you can commit changes to a docker container, read up how to do that.
Q3 - same. you can import directory with the -v option. the dependencies should never be an issue as you need to compile (mostly) static to fuzz a target effieciently
@vanhauser-thc thank you.
Could you please explain what happens if i don't compile my fuzzed targets as static binaries in terms of efficiency? If i statically build my targets, what about libraries like libdislocator and sanitizers? I thought it's better to use them for efficiency in bugs discovery.
Hi.
I've never used docker before :(
Q1
What i've come to so far is that to build AFLplusplus docker image, i should do the following:
Seems like
docker build
should be started as root, otherwise i receive error, that docker can't connect to docker daemon socket.Also
docker build
requires path to directory that holds Dockerfile.If that's correct, i suppose README.md needs to be updated accordingly.
Q2
I also noticed, that 32-bit libraries failed to build in docker container. Furthermore, in that case we're not able to quickly fix it by installing some additional packages and running
make
again, as AFLplusplus directory gets deleted at the end ofdocker build
process. :(Q3
I have built my image, and then i start container with this command:
There are afl-* binaries present with libraries like libdislocator.
How to use them? Should i somehow transfer sources of my tested projects to the container? In that case what about my billions of RHEL SourceRPM legacy dependencies?
Or should i take AFL binaries from container to my system? Neither of that?
Thanks in advance!
The text was updated successfully, but these errors were encountered: