GSoC 2023 #1098
Comments
|
Hi. I'm interested in "Start rewriting AFL++'s afl-fuzz in Rust as a frontend of LibAFL" in #119. |
|
Hello. I am working on #36 and will open PR soon. I am open to work on Rust projects and would like to contribute to LibAFL |
|
Hello, I'm interested in working with issue #777. I don't have much experience with libafl_frida but it seems a great opportunity to learn new and more about the subject. Can I use that issue's discussion topic for further doubts? |
|
yes |
|
Hey @tokatoka ! I am Shubhangi, an electrical engineering undergrad and a student developer from IIT BHU. I would love to contribute to AFL++. I am starting out in fuzzing and have beginner level experience in Rust. I am keen to contribute to |
|
Hello @tokatoka Soumya Ranjan here, and I am a third-year undergrad with proficiency in various tech stacks, including Rust, NodeJS, JavaScript, Python, PostgreSQL, MySQL, and C++. Currently, I am enthusiastic about contributing to the "Fuzzer template generator." project as a part of the AFL++ community. I am thrilled to be a part of this community and eager to make meaningful contributions. |
|
Yes Please send some PRs & contribute to libafl beforehand if you want to participate. |
|
Thanks for replying @tokatoka . So i have to set up my local environment for libafl and solve some issues to proceed further. Can you please help me by mentioning some good issues which are still open to get familier with the codebase. |
|
any issue with good first issue tag if you can fix #701 then it's really helpful for us |
|
#1084 is done |
|
The other 2 are still open along with #701? |
|
Note that ideally the wizard shouldn’t ask which components to use, but rather what kind of fuzzing the user is intending to do, and then suggest components/modes/capabilities that match. |
yeah you can work on any open issue (not necessarily good first issue) |
|
Hello @tokatoka Actually when following the contributing guide and running the "cargo build --release" command i am finding error and cannot able to resolve it out. Can you please help me with it |
|
do you have llvm-config |
|
Yes version 14.0.6 |
|
can you try things on this issue?
|
|
Hey @tokatoka are there any good first issues left? I would love to contribute to AFL :)) |
|
there're some issues with "good first issue" or "enhancement" that you can work on (and this is not AFL) |
|
Hello @tokatoka After making certain changes in code mentioned in that issue and this error still exist in code showing can you please guide me what to do? |
|
are you on windows? or linux? |
|
I am in linux |
|
Ok
Where does these 4 warnings come from? are you on mingw or something? (if it is mingw, then perhaps you'll need to find out what's missing. I guess nobody has tried running libafl on mingw) |
|
Actually i have dual booted with windows but currently i am in ubuntu linux. |
|
ah ok. so I'm sure is printing out file XXX is missing. can you find out what is missing in your case? |
|
Yes the warning come from println!("cargo:warning={:#?}", r) |
|
hmm |
|
Actually in if the condition is for unix so it is running for linux. and in else it is for windows |
|
ok that code is for windows can you revert that change and see what file is missing in your case? |
|
And when i run cargo build --release code it is only showing 4 warning err messages. not specifically showing due to missing of which files these errors are occurring |
|
if i modify the code in else if(windows) |
|
yeah I mean If you want to insert debug prints, you have to do it in do you have clang++ installed? |
|
No clang++ is not installed |
|
well, you have to install it to get it working |
|
After installing clang++ I have to build the code again? |
|
yeah |
|
But finding same error again at the time of building. I tried to restart my pc also but facing the same problem basically the only error that i am encountering since the beginning is, it is failing to run the custom build command of |
|
you need to find out what what file (dependency) is missing from your system to make it work I'd guess some header files are not present |
|
Yes some header files are not present |
|
Is there any specific version of llvm required? i have installed 14.0.6 |
|
no anything between 11 and 15 should work |
|
Actually i am also facing the same issue there is no stderr file exist in libfl_cc-xxx |
|
@tokatoka i have corrected the include header error but still facing the issue what should i do? |
|
You can send us the draft gsoc proposal to [email protected] beforehand so we can take a look |
|
Hey @tokatoka I am interested to work on AFL-style UI in #119. I am a beginner in rust and I have prior experience in TUI with python. I would really like to work on this to build my rust skills. Could you help me in providing some documentation and resources so that I could get up to speed. Thanks in advance |
|
Hey, @tokatoka and @soumya-78. I guess I found the solution. I was facing the same issue here, in my Ubuntu 22.04. First, the outputs of From this output I concluded the problem was in this command: The subsequent lines gave me some clues: First thing I did was check my clang++ installation using So even though I have clang++, sounds like it's not being able to find the source code of some included libraries (like "I ran into a similar problem after a system upgrade. After a while, I realized that it was because nvidia-driver-520-open installed gcc-12. I use clang-15 that I installed with the script installClang15.sh. clang-15 depends and hence installs libstdc++-11-dev and gcc-11. The problem is that once gcc-12 was installed, clang++ picked it up automatically instead of gcc-11... " The easiest solution is to add the missing And it worked! |
|
Probably you don't have libstdc++ |
|
@RougherO |
|
Yes. My great skills in editing big markdown files made me publish an incomplete answer hehe I choose to edit it instead. |
The text is a little difficult to understand, although I understood more or less of how its working it would be great if you could provide something which is a little more easier perhaps some examples would make it clear... Thanks |
Hello tokatoka, last Wednesday I sent my gsoc proposal draft to [email protected]. Do I have to send it somewhere else? Because I don't know if you guys received or are still analysing it hahahahaha. |
|
Sorry for being late |
No description provided.
The text was updated successfully, but these errors were encountered: