- It's the applications, stupid
- Will a whitelist save personal computing?
- Thousands of Web sites under attack
- To solve the unsolvable problem
- Re-thinking the security of virtual machines
- Security Development Lifecycle trumps code complexity
- Is your Web site FIPS compliant?
- Computer security: Why have least privilege?
- Strategic security: Get a handle on authentication
- Control user installs of software
July 17, 2006 | Comments: (0)
Win money and books for cracking my Windows password hashes!
$100 plus several of my books if you can crack my Windows password hashes.
I've been participating in an online thread discussing password complexity versus length. I say forget complexity and go for length. Many others feel complexity is the way to go. So to put my money where my mouth is, I'm sponsoring a contest:
CHALLENGES:
Let's do a test, with three challenges:
Challenge #1 (Complexity at 10 characters) for the first person to email me the plaintext equivalent to the following NT hashes:
Easiest Challenge: 0570B4C2CC734E230DE9B67C868FAE04
Clues Normal Password Cracker Would Not Have:
1. It's 10 characters long exactly
2. Contains no words contained in the English dictionary, but is based upon two words that have been "license-plated" (i.e. hybrid attack is needed)
3. Moderate complexity, but nothing beyond alpha letters and numbers.
Prize for Challenge #1:
1. Your name in my InfoWorld column
2. A free copy of my book, Honeypots for Windows (Apress, 2005)
---
Challenge #2 (15 characters long, no complexity) for the first person to email me the plaintext equivalent to:
Harder Challenge: 7B1FC86A9CD8955963E3930C42F4226F
Clues Normal Password Cracker Would Not Have:
1. It's exactly fifteen characters long
2. Contains one or more words contained in the English dictionary
3. Absolutely no complexity.
Prize for Challenge #2 for the first person to email me the plaintext equivalent
1. Your name in my InfoWorld column
2. A free copy of my latest book, Professional Windows Desktop and Server Hardening (WROX, 2006)
---
Challenge #3 (15 characters or longer, some complexity) for the first person to email me the plaintext equivalent to:
Hardest Challenge: 4475BCB3B66320BF289D5475C7016A81
Clues Normal Password Cracker Would Not Have:
1. It's fifteen characters or longer
2. Contains one or more words contained in the English dictionary
3. Some minor complexity.
Prize for Challenge #3 for the first person to email me the plaintext equivalent
1. Your name in my InfoWorld column
2. $100 out of my pocket (my wife is going to love me)
3. A free copy of my latest book, Professional Windows Desktop and Server Hardening (WROX, 2006)
4. A free copy of my next sole author book, Windows Vista Security: Preventing Malicious Attacks (Wiley, 2007), when it comes out.
(or you can substitute any of these books for my latest co-author book, MCSE Core Electives in a Nutshell (O'Reilly, late 2006) when it comes out.
------
Rules:
1. I solely determine winners and all rules
2. You can only claim one challenge prize. Send me the passwords if you break them, but if you win both challenges #1 and #2, I'll give you all the prizes listed in #2, but I'll give prizes in #1 to the next closest winner.
All password hashes can easily be cracked with the right tool and dictionary. I expect the first challenge to be cracked first. I suspect all three can be cracked. In the real world, the attacker would not be given the clues I have given. But I want readers to understand how hard this would be to do even if you had all the clues a real cracker would need to begin the attack.
This is proof of concept of password length over complexity. If someone breaks Challenges #2 or #3 before #1, I'll know I'm wrong.
Have fun and enjoy.
Posted by Roger Grimes on July 17, 2006 05:54 PM
RATE THIS ARTICLE:
-

- COMMENTS
Hi Roger. As the publisher here at WROX, I'd like to help you raise the ante on this. Contestants, be sure to read the additional prize you qualify for if you're one of the three winners to Roger's contest above. See my blog post at http://jwikert.typepad.com/the_average_joe/2006/07/wrox_author_con.html.
Roger, let me know what additional WROX books the winners choose and I'll be sure to get them to you.
Posted by: Joe Wikert at July 19, 2006 09:09 AMHi
I may not get the money or the fame, but thats not to say I can't crack your password, but not by the rules you have set out.
Precomputed NTLM tables do not exist for greater than 9 characters, even then separate tables have been built for lower / upper case as the combined size is circa 1TB. 10 characters, would rise expotentially. The quickest way to crack the challenge is to hack you / send you a key logger / wire tap your Ethernet or any other method. But even a simple brute force by your rules will take circa 4500 days for just lower case + numbers.
The tools available on the web are not 64 bit enabled, nor are they multiprocess enabled. There is an option within some tools to use more than one server /PC but by the time you get to 15 characters / mixed case, unless you are called the NSA / FBI / MI6 etc even the odd 1000 clients won't make a lot of difference to cracking the challenge within days rather than years.
If any one can crack the challenges, I think they deserver more than $100 due to the processing power they have used.
Posted by: Ade at July 25, 2006 10:24 AMWhat really gets me is when I open an account and try to find a password that no one can figure out. The next day I get an email that says thanks for opening an account with us your user name and password are. Don't loose them. So all someone has to do is read my email and they have my password. Your user name and password should not be sent to you unless requested.
Posted by: Terry at July 26, 2006 04:02 AMIn response to Terry's comments, I don't think the password and user name should be sent even if the user request it. I think the user name and password should be set to a one time version, and a link should be emailed forcing you to reset your username and password. Websites should also require the user to change their passwords every 30-90 days.
Posted by: Ken at August 10, 2006 12:50 PM






