Open source as a reward for the JS Fuzzer

Tuesday, 7 August 2007

Did you like my JS Fuzzer? If you did, then leave a comment here and when the site reaches 30 unique comments for this post I shall release the source code. You can then run it for as long as you want on your own server.

Once the source code is released I shall be creating a Google group to continue development work on the fuzzer. So if you’re interested in joining the team let me know in a comment.

So if you want the code, tell your friends to visit the site and try out the fuzzer πŸ™‚

JS Fuzzer

Update…

Half way there everyone πŸ™‚ Thanks for all the contributions so far. I’ve updated the fuzzer as well to include randomisation and run until javascript execution.

Further update

1. Run until javascript execution, you have to hit ok for now but I plan to remove the need for reposting as well.
2. All execution is logged into a database that I shall release for everyone once I’ve cleaned out all the invalid ones.
3. The script also now allows you to randomise all options and characters for every row.

The entry 'Open source as a reward for the JS Fuzzer' was posted on August 7th, 2007 at 2:06 pm and last modified on August 8th, 2007 at 10:58 am, and is filed under javascript, php, Security. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

32 Responses to “Open source as a reward for the JS Fuzzer”

  1. Ben writes:
    No. 1 — August 7th, 2007 at 2:58 pm

    Blatant attempt at driving up blog traffic!

    Oh well, it worked. One unique comment here.

  2. alban writes:
    No. 2 — August 7th, 2007 at 3:16 pm

    I think I’ll add my comments to reach the 30. This is really interesting !

  3. tenest writes:
    No. 3 — August 7th, 2007 at 3:21 pm

    I’d definintely like to see the source. count me in.

  4. head writes:
    No. 4 — August 7th, 2007 at 3:25 pm

    i’ll bite… good stuff, but why the 30 posts requirement?

  5. geetarista writes:
    No. 5 — August 7th, 2007 at 3:51 pm

    Thanks for the great tool!

  6. Eric Thelin writes:
    No. 6 — August 7th, 2007 at 4:40 pm

    Interesting

  7. Michal Till writes:
    No. 7 — August 7th, 2007 at 7:56 pm

    Hi, absolutely! Thanks a lot!

  8. .mario writes:
    No. 8 — August 7th, 2007 at 8:53 pm

    this is just an increment from 7 to 8 πŸ˜‰

  9. anonymous writes:
    No. 9 — August 7th, 2007 at 9:34 pm

    Out of curiosity, what happens if someone comments who has NO interest in the fuzzer? πŸ˜‰

  10. anonymous writes:
    No. 10 — August 7th, 2007 at 10:24 pm

    What is Fuzzer?

  11. Gareth Heyes writes:
    No. 11 — August 7th, 2007 at 10:40 pm

    LOL anon, I’ve no way of proving that they are unique comments, but if you want the source code that bad I’m not going to stop you πŸ™‚

    If you are serious, there’s a link on wikipedia :-
    http://en.wikipedia.org/wiki/Fuzzer

    I’m just doing this experiment to see if I could gather interest because I have taken the time to write the code, I don’t really think 30 comments are a huge target to hit and you would be giving something to the site in return for the source code.

  12. 0x000000 writes:
    No. 12 — August 8th, 2007 at 12:14 am

    Encouraging people to spam? πŸ˜‰

    Well, I don’t need the fuzzer still I want to help the rest to reach the 30 comments πŸ™‚

    Nice guy ain’t I ? πŸ˜€

  13. etng writes:
    No. 13 — August 8th, 2007 at 3:07 am

    Hi,I am sorry that I can not catch what Is Your tool used to do.
    Can you give more links or documentations?thanks.

  14. ensi writes:
    No. 14 — August 8th, 2007 at 6:55 am

    Some source code would be interesting…

  15. absa writes:
    No. 15 — August 8th, 2007 at 9:26 am

    in soviet russia releases comment you

  16. Ken Guest writes:
    No. 16 — August 8th, 2007 at 9:57 am

    I’d certainly be interested in looking over the code – might even put it to good use πŸ˜‰

  17. Michael Johnson writes:
    No. 17 — August 8th, 2007 at 1:26 pm

    I haven’t had a chance to try it out yet, but I’ve been thinking of trying something like this out on our internal code. I would really like to have something I can build into our development process.

  18. Matthew Pettitt writes:
    No. 18 — August 8th, 2007 at 3:31 pm

    30 comments is cheaper than employing monkeys to hammer on the keyboards, so it’s got to be a worthwhile deal…

  19. Gareth Heyes writes:
    No. 19 — August 8th, 2007 at 3:46 pm

    I’ve Just added a bunch of new features to the fuzzer now, you can add random spaces and enable, disable events, styles etc, we now have a database as well πŸ™‚

  20. Justin Patrin writes:
    No. 20 — August 8th, 2007 at 5:15 pm

    Another comment to add to the pool.

  21. db writes:
    No. 21 — August 9th, 2007 at 11:06 am

    Looking forward to it

  22. akash writes:
    No. 22 — August 10th, 2007 at 5:18 am

    Comment number 22

  23. dita writes:
    No. 23 — August 11th, 2007 at 8:36 am

    Show some code πŸ™‚

  24. Mala writes:
    No. 24 — August 12th, 2007 at 7:37 pm

    Yeah, code please πŸ™‚

  25. Andy writes:
    No. 25 — August 13th, 2007 at 1:47 pm

    Go on then, consider my arm well and truly twisted πŸ˜‰ Seriously though I’d love tot see the source code

  26. nigon writes:
    No. 26 — August 13th, 2007 at 4:07 pm

    I would like to review the code. Thank you.

  27. La^^&r writes:
    No. 27 — August 13th, 2007 at 8:29 pm

    Show us the code! πŸ˜›

  28. Gareth Heyes writes:
    No. 28 — August 13th, 2007 at 8:50 pm

    Get two mates to comment and the code is yours πŸ˜‰

  29. 29 writes:
    No. 29 — August 14th, 2007 at 11:01 am

    29 : )

  30. pF ;) writes:
    No. 30 — August 14th, 2007 at 6:02 pm

    Thanks.

    Γ ΒΉβ€œΓ ΒΉΒ πŸ˜‰

  31. Gareth Heyes writes:
    No. 31 — August 14th, 2007 at 7:57 pm

    Thank you all for your support, I am writing a new blog post with instructions on how to get the code as I write this.

    Please get involved with the project.

  32. Gareth Heyes writes:
    No. 32 — August 14th, 2007 at 8:32 pm

    Source code released! Thank you again for your support.

    Source code

«
»