Topic: Mt. Gox Hack claims (Read 9169 times)

Solution to crappy password management

-Create a truecrypt masterkey file: with one sick ass long 50 char pass wich you will save in your mind.  (http://www.truecrypt.org)

-Create a bunch of txt files within in the mounted truecrypt dir with 0 untill 9 digits as filenames.
So:

0.txt
1.txt
2.txt
etc...

-Put in each txt file a generated pass wich is 10 chars minimum.

-Pick a number you like with 3 digits or more.

-Paste each password in the #.txt file behind each other based on the 3 digit code you will remember.


-Go to lastpass.com (www.lastpass.com)

-Download tool.

-Create account

-Use masterkey as master password

-For each website you register in the future... use a 20 digit pass you can generate with lastpass.

-Make a list of all websites you think are important to change the pass.

-Take an hour and change each pass and let lastpass generate one for you.

-Put masterkey file on each hardrive/usb stick you got.

-Done

Can I pay in Bitcoins?

Already at 10 characters alphanumeric, the possible number of combos is 839299365868340224. @5 Ghash/s, it would take over 5 years to go through them all, and each additional character multiplies the time by 62.

Yeah, that'd do it. That information either wasn't posted, or hadn't caught my attention when I posted before - note there's 2 hours between my post and yours.

16 character alphanumeric. MD5 can be weak as snot, unsalted, and exposed via SQLi and I don't care.

Don't be sloppy with password management!

All of you re-using passwords between sites, re-using usernames and passwords between pools or miner accounts, re-using same email addresses across forums and exchange accounts, ALL OF YOU ARE ASKING TO GET PWNED!

What will it take for this message to sink in? cracking the MtGox hashes shows the majority of you are still being lazy...

yep the DB was leaked and has been confirmed it has 61020 entrys  with your username email address and a hashed password atlest the passwords where not plain text

its a trick.. Those are the real passwords just happen to be the same length as a hashed password

oops

Rainbow tables != reverse lookup tables.

It's stupid as fuck banking on MD5 - either the plaintext for those hashes is really long and/or not actually alphanumeric, or he's going to be some 80BTC poorer in a couple weeks. If they really are <16 chars, unsalted and alphanumeric, I'd be willing to bet the 80BTC is probably worth more than what you'd spend on some Amazon EC2 instances to break it in a hurry...

It's also stupid as fuck chaining multiple rounds of MD5 together, particularly without changing the salt each time. - I believe you actually make it weaker to rainbow table attacks by doing that... but I'm absolutely no expert in cryptography by any stretch of the imagination.

Regardless, if there's any evidence at all that the DB is taken, assume the passwords are broken. Now where's the credible evidence the DB was taken?

Well they aren't in any rainbow tables, so they must be pretty long. Judging by the high reward on this, he probably used 15-20 characters. Enough that you might as well keep your computers mining bitcoins, it could be months even for a very powerful group of computers.

While I'd agree that it seems likely the offer of the database for sale is a fake and just intended to shake confidence in Mt. Gox given all of the other activity that's going on, MagicalTux's response doesn't instill much confidence. In fact suggesting things like salted hashes would protect the passwords and no suspicious logins found sound exactly like the kinds of reports that come in early from actual intrusion victims. Most salted hash schemes in use won't protect people with weak to crack passwords, which will be about 99% of the users, and a SQL injection compromise which is by far the most likely approach wouldn't involve OS logins. The fact that there was a recently discovered CSRF hole lends credence to the idea that there could easily have been a SQLi. And while he may be playing dumb, he doesn't sound like he has the instrumentation in place that would even necessarily allow him to discover an intrusion like that after the fact, even if he knew what to look for.

So while it's only smart for him to categorically deny any intrusion he doesn't have direct evidence of, and I'd still rate the HN post as much more likely to be fake than real, I'd still personally change my password all the same.  Tux really couldn't give you that advice unless he'd already found and closed a flaw without tanking his business.

Exactly my point.

MagicalTux has already responded to these false claims via IRC:

Rainbow tables exist for 10character alphanumeric... they're only ~320GB.

Challenge accepted.

Password changed. (it had been a length of 50 and will now be as well )

To be honest I don't care if the account gets hacked since I don't have anything there. (the biggest job is to keep your wallet secure)

Unlikely unless you're sloppy.

To prove the point, 10 bitcoin for each pass for any of these unsalted MD5s:

824cfad07c88261afb4dd3285627887a
73550477b12849b2a4dcd3b0db187415
3e567bcbb2aa5c28c47012b857bf6e48
3709fb6b0e1c0b26ff22a19ae92fd080
9133c451dd761d29943dcc653252e2fa
ff111d6144367b4abd99aa4321b0a618
8602188ef5a05a13afc59c51b395426c
da842aa7c84236d17a04098fa1273f2d

Have fun! ;P

EDIT: alphanumeric only. I'll pay legitimate finds or my name is mud!

Multi-round hashing is just a simple loop. For example:

$password = 'shortcut' .$salt;
for($counter=0; $counter < $round; $counter++) {
     $hash = md5($password);
     $password = $hash;
}

If you're using dictionary words - even if there's numbers & capital letters, there's a high chance your password will be found. Hybrid dictionary attacks process a shit ton of passwords/second regardless of how complex the md5 & salt equation is.

how strong was your password?