Is fuzzing important?

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


Mar 9, 2024

This is an article about using a (?) new fuzzing app (SR Fuzzing) to detect vulnerabilities.

I stumbled over this article and other than hearing that fuzzing is involved in security, know nothing about it and am curious if it is significant.

The authors are all Chinese from Chinese institutions, for what it is worth.

If this is a new/useful tool, I would like to know it <g>.
Fuzzing is usually a "destructive testing" approach. It's basically taking a known good input to a program, and then modifying it algorithmically (or randomly) and then sending it into the program to see if any breakage can be detected. It's something developers SHOULD use and white hat security researchers do use, but it's not really something valuable for end users.
Thanks for clarifying. As a noobie, I have no basis for judging if the fuzzing tool described is better in any way than conventional fuzzers.