-
Notifications
You must be signed in to change notification settings - Fork 83
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
Magma build failure (and other issues) #24
Comments
Please check the Troubleshooting section on the Magma website as a first step when facing problems.
|
Update: I've gone ahead and updated the Check out the documentation for requirements, usage, and sample output. |
Hello @hazimeh ! Thanks for your reply . After a lot of investigation I came to three commands which basically solved my problem on docker permission things . so, I highly recommend you to add these commands to top of this getting started page, so no-one will get disappointed from this permission problem stuff :
If you can add these commands to : I'll appreciate you! I mostly interested in running this interesting bench tool as a local tool so if you can also make just one bash script to install all dependencies need for all these toolset, it's much appreciated, running too much scripts one by one is a bit cumbersome . Also, if you can provide all those vulnerable targets as a corpus for those of people who are interested to run them against their fuzzers out of MAGMA toolset (exactly Like LAVA) it would be nice! I'll let you know the results of running a test with magma and if that was going fine, I'll close this issue. Thanks again |
From the output I got from Magma, it seems it runs well on afl and aflplusplus but failed at running and building symcc . For all of these stuff, I used captain because it was easier to run . Does using captain mean that the tests will be done at the local machine or it just mean in an unmanaged manner ? Also I would like to know, how is it possible to generate beautiful reports from MAGMA like this for campaigns ?
Thanks |
Will do. Thanks for the feedback.
Could you attach the full build log for the symcc_afl image?
The captain toolset automates the process of building, running, and scheduling Magma Docker images and containers. The experiments run on the local machine, but within a containerized process. This could induce some syscall overhead, but all fuzzers are evaluated within the same environment (a docker container), so they're all subject to the same overhead. syscall-heavy fuzzers are technically at a disadvantage, but that's not due to the containerization; it's just because they're syscall-heavy.
I'm still in the process of reviewing PR #22. Currently, the generated reports are tightly coupled to the CSS stylesheets on Magma's website. I'll need to look into a more suitable way to publish these reports. |
Thanks for your explanations .
I don't know when you're going to make change and make working scripts for report generation but I used the reports branch in the current magma and after successful running of afl and aflplus against libpng for report generation I have the following problems :
The json generated files with benchd scripts is as :
Is it mean that the scripts are not working as expected or there are other problems around ? Thanks! |
Have you tried using the new "exp2json.py" script instead? Just point it at the I think the issue with the attached JSON file is that the "logparse.py" script may have been pointed at the wrong root dir. Try the "exp2json.py" script and let me know how it goes. |
Using the "exp2json.py", I have the following erros : (using branch v1.0.4)
I think a complete documentation is also necessary for that report and bench tools stuff . |
Another test with the latest branch :
And about symcc issue to install locally, I installed a new clean ubuntu 18 vm and after using fetch.sh and build.sh scripts things are as : (Have nothing inside, just used magma scripts to install everything but seems not working)
|
@hazimeh |
It's possibly an edge case where the monitor log is empty (premature campaign). I'll address it when I get the time. |
@cryptomadco Could you please archive the workdir and attach it here? I'd like to reproduce the error. |
@hazimeh If you get a working report of this , please let me know how to setup for that report . Thank you |
Alright, it seems the error was due to an empty monitor log for |
@hazimeh |
Could you also attach the |
Yes, this was my captainrc :
|
The TARGETS configuration parameter requires a fuzzer prefix which matches the fuzzers being evaluated. In your case, you would need to specify them as follows:
|
Thanks a lot, but I didn't find that keywords in the documentation, I just thought all will be done with afl_TARGETS . just think that it's better to add one more keyword for this in Now going to run that . @hazimeh Do you possibly know approximately, how much does it takes for you to check and fix that web report tool to a working version ? Thanks! |
I am currently in the process of merging it. It will take a while, however, as I need to proofread the code and make sure it works correctly. I'll ping you when it's done. |
Thanks about that, further discussion about that report tool also can be take through mail, some days ago I pinged you over you@epf.ch , just don't know if you receive that and get time to read that . Thanks! |
Now, seems the There is just one problem reaming that is related to that report tool :
As I tested Magma in recent days, I think magma with a working version that web report tool, is a cool fuzzer evaluation tool! |
@cryptomadco I have merged and partially tested the report-generation code. In its current form, it is only able to generate plots:
I hope I am not missing any requirements. Edit: It's on the |
Too much appreciate Ahmad! the plot generation is working well, tested it with different scenarios, works like a charm! thank you very much ! I think that the Symcc_afl had some modifications so I have problems after running the campaign with ./run.sh , it's the log of
failed for other targets for symcc_afl as well . Thanks! |
@cryptomadco I forgot to mention, the campaign duration used for plot generation is currently hard-coded (in seconds) in |
Hi . On the other hand, whenever I want to generate reports, I get the following :
Currently, I run the test in 2 hours cycles, also I fixed what you mentioned about seconds in
Thanks! |
Hello .
I tried many time to setup magma .
I want mainly :
This is the log after running ./run.sh in the captain dir and I don't know why it's not running .
I want to build a vulnerable target (say libpng) with my own fuzzer and have reports as in the magma documentation, how is this possible ? (As easy as changing scripts or the fuzzer should be built into a docker ?)
While setting up symcc_afl I got the following error :
How to solve and build symcc_afl ?
Thanks!
The text was updated successfully, but these errors were encountered: