5 ms·
> a password of length 40 would cost $200K to crack I'd love to see someone try. Here, an md5, those are super vulnerable right? This is a 9 character password
by lucb1e 13y ago
> a password of length 40 would cost $200K to crack
I'd love to see someone try. Here, an md5, those are super vulnerable right? This is a 9 character password. Piece of cake if I should believe the news.
f1f107c27cae21b5b5b01002e9c9ead8
- explorigin 13y agoWell, Google search reveals nothing. I'm done.
- lucb1e 13y agoLol yeah that's how I usually check md5 hashes too. But that doesn't work: this is from /dev/urandom while filtering out only /[ -~]/. It seems people don't like that I'm proving the point by a super simple example though. And yes, my passwords are as strong as this, I don't use text passwords. Cracking 40 character passwords is absolute bullshit.
- comex 13y agoMisinterpretation, not bullshit. Per another reply, the original document was about 40 characters of English text.
- lucb1e 13y ago> Misinterpretation, not bullshit. Fair enough. I'm still curious about the generation method though: I can imagine that testing all texts ever published takes $200k if you go up to 40 characters, but if you use a unique text it might be different. There are a lot of variables here, including honest misspellings, punctuation use, spacing (non-tech people seem to find spaces weird in passwords), capitalization, usage of names, etc.
- tracker1 13y agoMaybe if we start changing the label to "Passwords" or "Pass phrase" to indicate that you can do something more expressive. It bugs me that even today, more systems (hello banks) don't support more open passwords. Even what's on a US Ascii keyboard would be nice. Two of my banks only support letters and numbers, no special characters and case insensitive.
- Confusion 13y agoYour passwords are as strong as the protection of the place where you store them.
- drblast 13y agoSome numbers for you. Using non-optimized, managed code on my laptop, I just went through 250 million iterations of plain text in ten minutes. You didn't specify what counts as a character, but let's assume it's a printable ASCII character. 95^9 = 630249409724609375 possibilities. Divide by 250 million, and we get about 2520997639 times ten minutes for the time it would take me to enumerate all possible plain text passwords. That's a long time, about 47000 years. Not going to happen today on my laptop. But if I were a government, maybe I'd get a few thousand laptops together and set about calculating this over the next five years or so. In 1997. But if I were to throw some purpose built hardware at this problem or use the video card to speed this up and not just laptops with general purpose CPU's, it's very likely I could decrease this time by thousands of times. At the end I's have all MD5's for all passwords, and now the problem becomes a rainbow table lookup. And I only have to do this once and I forever gain the capability to break any 9 character (and below) password with just a lookup. And that's assuming that MD5 is a perfectly secure hash with no shortcuts allowing you to narrow down the input set.
- xhrpost 13y agoDid some more calculations just for the fun of it. It looks like you'd need nearly 16 exabytes of storage to hold the MD5 table for every 9-character hash [1]. Not accounting for any database overhead. In high density, you can fit a petabyte in what now a days? Half a rack? So around 8,500 racks. Certainly in the realm of possibility for a government but it would be a lot for storing just one type of hash list. [1] https://www.wolframalpha.com/input/?i=%28630249409724609375+*+25+bytes%29 https://www.wolframalpha.com/input/?i=%28630249409724609375+...
- mattdw 13y agoI feel like there should be a more efficient way to store these things. You have a complete enumeration of possible inputs (passwords), but unfortunately we need to go in the opposite direction, so we couldn't just index into a n*9 bytes array. Depending on how well distributed the md5 hash space is, it's possible a prefix tree might save you a bit of storage (you'd only have to save a couple of bytes per entry to cancel out the overhead) but I couldn't tell you the numbers there. Otherwise I think you're right, and we'd just have to store a map of md5 -> password. (Edit: Also being limited to alphanumeric for hashes and printable ascii for input gives you pretty good compression potential.)
- jtheory 13y agoYou say "9 characters" -- is that "printable characters", or alphanumeric, or what? If you have a decent GPU, you can try several billion MD5 hashes per second: http://www.golubev.com/hashgpu.htm http://www.golubev.com/hashgpu.htm -- so if you stick with, um, lowercase alpha only should be crackable in under 10 minutes. If you choose from the 95 or so printable ASCII chars, you can expect a bit more of a wait (possibly a few years)... though of course if you don't restrict yourself to a single GPU you can speed things up. Honestly, using an actually-random password that's more than 8 chars and not just alphanumeric offers decent security even when it's stored with a fast hash algo. Unfortunately, very few people do this in practice, and instead choose (for example) one of the 43 billion passwords in the md5 database here: http://www.md5decrypter.co.uk/ http://www.md5decrypter.co.uk/
- unfamiliar 13y ago"Just to prove some guy on HN wrong" is not much of an incentive to spend the required resources. It says nothing about the ability to crack MD5 when there are significant incentives. Why not md5 your credit card info and post it here if you are so confident?