SN 908 Made up words

  • 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.)


Active member
Sep 29, 2020
I was beside myself with glee 🤓 to learn after all these years that Steve uses the same password generating technique that I do. Making up nonsense words (with additional numbers and characters). I've long suspected that he might be the sort of guy who makes up silly words (diddly doodly). ;)
A couple thoughts: Some of my old nonsense words are too short by today's standards. Also, some of the words we might think are our own creations might really be something from an old TV show we remember from childhood (e.g. ack-acka-dack-dack-dacka-ack).
But this brings me around to where I keep getting mixed up. (I hope I'm using the right terminology) If my password can be 65 characters, upper/lower case, numbers and specials then the search space is very large. If my password is combined with a unique, used only once, pseudo-random Salt and hashed properly, then it's existence in a precomputed Rainbow Table is (highly) unlikely.
If an attacker gains access to a company's collection of properly encrypted passwords, and she singles out the hash that corresponds to mine, she would not only have to guess my password in it's entirety, but also the salt. In other words, wouldn't the hash of "monkey1234" look as much like gibberish as on of GRC's Perfect Passwords? I don't understand how Leo's comment about frequency analysis would factor in, unless the attacker could go character by character. Obviously she will try "monkey1234" long before a Perfect Password. But in a bizarro world where monkeys don't exist (Like in German).

Chapter 8 from Jasper van Woudenberg and Colin O'Flynn's book, The Hardware Hacking Handbook, is available for free from No Starch. If I understand what they're saying, then you can go character by character in a timing or power analysis attack. But that's not what an attacker who grabs a password list from LazySecurity-dot-Com would be doing, is it?
but also the salt
No, salt has to be stored with the password so it can be used when verifying the password. For example, if you look at a record from a Unix system, you would see something like:
The salt is 56YsS//DE (the format is $5$ which is SHA256 and the password hash starts with HasM6O8y2mnXbtgeE64zK (the record is truncated.)

Salt only provides a way to prevent to users with the same password from having the same password hash... it's just used to prevent lookup tables (rainbow tables) and not really to provide extra password strength.
  • Like
Reactions: Badrod