Closed zhangysh1995 closed 5 years ago
And because the default parameter -t
for timeout in AFL
is changed, could I still have a way to set time limit?
I have the same issue when following the instructions to fuzz base64
inside the docker container
.
Have you ran echo core | sudo tee /proc/sys/kernel/core_pattern
?
I already ran echo core | sudo /proc/sys/kernel/core_pattern
on my server. And I could run AFL
smoothly on the server. Is there any differences between this command and the one you gave?
The content of the file on the server:
yushanzhang@ubuntu:~$ cat /proc/sys/kernel/core_pattern
/apollo/data/core/core_%e.%p
And it is difficult to get this command run inside a docker container
, because docker doesn't allow it. One explanation is here.
This is content of the file inside the docker container.
root@f8a44c8e576a:~# cat /proc/sys/kernel/core_pattern
/apollo/data/core/core_%e.%p
Angora checks your core_pattern
's content to ensure if it is core
. Obviously, it is not core
in your server.
Please run this command outside of docker, and restart the docker container again.
I followed the tutorial in docs to build LAVA-M, and use the following command to fuzz
base64
:And it crashes on startup, and shows this message:
Is this problem related to core dump mode? But it is required by
AFL
, so this was already set before. How should I fix this poblem?