Please don't use 7zip for compressing the file to 1245 bytes. It's not going to happen. After many frustrating attempts, I just used the software mentioned in the tutorial and achieved the compression almost immediately. Then I pkcracked it in less than five minutes.
-- Sun Mar 28, 2010 3:26 am --
I'm trying to get past the blank message part. I understand that I need to make the regular expression evaluate to true. I used TamperData add on on firefox to send some strings to the script but nothing happens, I get a blank page.
Q1.When I do the same thing using a Perl script I'm able to see the error message. I don't know why can't I get this error in a browser. What's going on?
-- Sun Mar 28, 2010 6:27 am --
Q2.All right, I can't proceed beyond this point since the solution that works on my computer doesn't work on the server. This regular expression matches everything (of a large length) using only the allowed characters. I have no idea why it doesn't work on the server:
Perl script
- Code: Select all
#.[(*$^+\| are not allowed
my $x;
foreach $i (a..z,0..9,A..Z) { #Each character or digit can appear 0 or any number of times consecutively
$x .= "$i\{0,\}";
}
$x .= "!\{0,\}@\{0,\}#\{0,\}%\{0,\}&\{0,\}_\{0,\}-\{0,\}=\{0,\}`\{0,\}~\{0,\}"; #Now I put symbols
$x .= ";\{0,\}'\{0,\}]\{0,\}}\{0,\}<\{0,\}>\{0,\}:\{0,\},\{0,\}";
#$x .= '\)\{0,\}"\{0,\}\/\{0,\}?\{0,\}'; These symbols cannot be put in the string without using the backslash (which is censored). Hence I've commented it out
$x x= 100; # Repeat the entire construct a 100 times
-- Sat Apr 03, 2010 5:23 am --
I've finally completed the mission. Regarding my previous regular expression query, the only reason I believe it doesn't work is because HTS doesn't accept that particular solution. Please correct me if I'm wrong, because in my opinion the solution using the regular expression generated by the above script is more general than the one given in the tutorial. I noticed that the characters { , } were not censored by the script so I could use "{0,}" as a substitute for "*". I believed that this was the method because those particular characters were conspicuously not censored.
If you have got to the point where you need to crack the double MD5, remember that the first MD5
crack must produce a 32 bit value (because the first MD5
encryption would have produced a 32 bit value). MDCrack won't allow my CPU to crack values 32 bits in size so I used an online MD5 database. A database doesn't compute, it just saves time if the hash has been cracked before.
The last part of the mission is using a buffer overflow. The method for breaking it was obvious to me after reading the Buffer Overflow articles on this site.
I however am still looking for the answers to Q1. and Q2.Best of luck.