It was originally created for the purposes of adding the hover onmouseover, but I also decided to add the alternating row color at the same time.

To be completely anal, I'll note that the hover is something that should be done with javascript (it pretty much has to be done in javascript anyways, and it's less part of the presentation than an action), while the alternating colors should be purely CSS.

However, this makes page creation easier. I also remember having some problems with reading the background color style from the row object, so this makes it easy.

It uses behaviour.

So I came up with this quick hack that should probably be fleshed out a lot more. Basically, you set up the image as you normally would, but give it a special class and a sort-of special name. Once the page is loaded, javascript looks through for all images with that class, uses the .src to figure out the name of the hovered version, preloads it (for caching), and attaches the requisite onmouseover and onmouseout events.

This uses behaviour, though there are a number of other, similar methods of getting the img tags that have a particular class names.

I was lucky, though, because I remembered what I would have done to this password (preface, postfix, letters -> numbers, etc). It ended up being few enough permutations to be reasonable but too many to try manually.

Basically, I just set up some arrays for the positions which may differ. I loop through these arrays, concatenate together a password, and try it. Everything is written to the terminal, so you just look for the entry with the very obvious success message.

If you're in a similar situation, you can modify the following script to crack your dmg file.

This perl code assumes that your default password is 'hello', and that you might preface or postfix it with nothing, 3, or #, and that the l's might become L's, 1's, or !'s.

PLAIN TEXT

PERL:




#! /usr/bin/perl -w


 


@preface_num = ('', '3', '#');


@first_l = ('l', 'L', '1', '!');


@second_l = ('l', 'L', '1', '!');


@postfix_num = ('', '4', '$');


 


foreach (@preface_num) {


  my $first = $_;


  foreach (@first_l) {


    my $second = $_;


    foreach (@second_l) {


      my $third = $_;


      foreach (@postfix_num) {


        my $fourth = $_;


 


        my $password = $first . 'he' . $second . $third . 'o' . $fourth;


        my $cmd = "echo -n '$password' | hdiutil mount /Path/To/Image/secure.sparseimage -stdinpass";


 


        print "Trying $cmd ...\n";


        system ($cmd);


      }


    }


  }


} 

This was good enough for me, though it would be a lot better if stderr were redirected to null, the return code was tested, and it only printed the successful password.

However, this blog is different... really. This isn't borne from a need to rant, but a need to share (see). Specifically (at least for now), it's code snippets and the like from my development exercises.