Skip to content
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

How to fuzz a application written by myself? #3

Open
jiak94 opened this issue Oct 9, 2016 · 3 comments
Open

How to fuzz a application written by myself? #3

jiak94 opened this issue Oct 9, 2016 · 3 comments

Comments

@jiak94
Copy link

jiak94 commented Oct 9, 2016

I replace the heater.c with the program I wrote, but it seems like it does not work. I read your blog but didn't find any tutorial on that? Could you give me some hint? Any help will be appreciated.

@timnewsham
Copy link
Collaborator

The problem is that the heater isnt being invoked currently. Look in the rootTemplate/init script and notice that the heater is commented out. You can uncomment it if you include a heater and test cases in your root template. You can also replace it with any sort of heating program you want to execute.

@jiak94
Copy link
Author

jiak94 commented Oct 10, 2016

Thanks for your reply. According to your post, I pack the heater, and inputs to my root template by uncomment the cp heater "$name/bin/heater and add cp -r inputs "$name" in makeRoot script. Then I modified the rootTemplate/init by adding /bin/heater inputs/*. It seems like the argument is not changed during the fuzzing. I use runTest to test the testcases generated by the fuzzer, no matter which testcase was feed, the argument for heater is always "inputs/*"

@timnewsham
Copy link
Collaborator

timnewsham commented Oct 10, 2016

It sounds like inputs/* doesnt expand to anything in your case. Try fixing the path to something like /etc/inputs/* if you have your heater files in "/etc/inputs". Also make sure your rootfs gets regenerated from the template (you might have to remove your old one to force it to be regenerated).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants