25 Gpus brute force 348 billion hashes per second to crack your passwords _ hackaday bitcoin price nz

It’s our understanding that the video game industry has long been a driving force in new and better graphics processing hardware. But they’re not the only benefactors to these advances. As we’ve heard before, a graphics processing unit is uniquely qualified to process encryption hashes quickly (we’ve seen this with bitcoin mining). This project strings together 25 GPU cards in 5 servers to form a super fast brute force attack. It’s so fast that the actual specs are beyond our comprehension. How can one understand 348 billion hashes per second?

The testing was used on a collection of password hashes using LM and NTLM protocols. The NTLM is a bit stronger and fared better than the LM, but that’s not actually saying much. An eight character NTLM password will fall in 5.5 hours, while a 14 character LM hash makes it only about six minutes before the solution is discovered.Bitcoin price nz

of course this type of hardware is only good if you have a copy of the password hashes themselves. Login protocols will lock out after a certain number of attempts and have measures in place to slow down automated systems like this one.

[via boing boing] posted in security hacks tagged gpu, hash, lm, ntlm, password post navigation

Hi, I’m jeremi gosney, the subject of this article. I see a lot of misunderstandings in the comments, and I have selected a few for response:

> “sure, using a lot of hardware to compute hashes is neat and all, but I want to find that motherboard that has 8 PCI-express x16 slots.”

The one large rig is a TYAN FT77B7015 barebones, the other systems in the cluster are primarily chenbro RM41300-FS81 + gigabyte GA-990FXA-UD7.

> “there are lots of bitcoin fpga mining farms 10 – 100 times more powerful than this..”

bitcoin price nz

FPGAs are great for brute forcing a single raw cryptographic hash — which is why they’re great for bitcoin mining. For something as dynamic and flexible as password cracking, fpgas are less than optimal. FPGAs do not provide the flexibility needed to support multi-hash, multi-algorithm, and multi-attack modes. The complexity of password cracking demands something in the middle between CPU and FPGA, and gpus are by far the sweet spot.

> “useful if you have the hashed passwords. If you can get those then the security’s not up to scratch anyway.”

You say that as if it’s hard to obtain hashes. It is not uncommon to exploit vulnerabilities which only grant some level of read permission, without the ability to obtain a shell or escalate privileges. KoreLogic estimates over 467 million password hashes have been leaked in the past year, not including stuff on pastebin.Bitcoin price nz cruise on over to insidepro’s forums sometime.

There is also the legitimate side of hash cracking as well, such as penetration testing and domain auditing.

> “how big a room can one of these heat?”

I don’t know, it’s not exactly sitting in my house. It is in a proper datacenter.

> “to be fair, NTLM can hardly be considered a cryptographic hash. It’s full of flaws, and can be broken very easily. Not to mention the complete lack of salting, which allows a simple rainbow table to crack it in minutes if not seconds. Why people continue to use it, I’ll never know. A real benchmark would be crunching SHA-256 or 512 hashes.”

– AND –

> “bit of a waste for cracking NTLM. Just download the rainbow table and can do the same thing with much less processing power.”

Well no, NTLM cannot be considered a cryptographic hash, because isn’t a cryptographic hash.Bitcoin price nz the NT hash algorithm employs MD4, which is a cryptographic hash. MD4 is in fact a broken cryptographic hash; however, its cryptographic strength has nothing to do with why it is a poor choice for hashing passwords.

Rainbow tables are great if you only have a couple hashes, and are sure the password is less than 8 chars. When you have an entire AD dump of 60k+ hashes however, rainbow tables are way too slow, even if you are using GPU tables and ssds. And of course the fixed length of rainbow tables is also problematic. We have the flexibility to crack passwords of various lengths and run multiple attack modes.

Anyway, I’m not sure why the media chose to focus on LM/NTLM. We support all 45+ algorithms supported by oclhashcat-plus and oclhashcat-lite. We have posted full benchmarks for -lite on the hashcat forums.Bitcoin price nz we will be posting benchmarks for -plus soon as well. The media is also focused on brute force times, and the cluster supports far more than just brute force. Indeed the cluster supports everything that hashcat supports.

> “even microsoft admits NTLM is weak and should not be used”

You are confusing NTLM with netntlm, netntlmv2, NTLM challenge/response, etc. When we say “NTLM hashes,” we are referring specifically to passwords stored using the NT hash algorithm, which is how all windows passwords — both local and AD domain — are stored at rest. There is no alternative to using NT hash on windows systems, including windows 8 and server 2012. This has nothing to do with netntlm.

> “ditto. Cool setup but not nearly fast enough to crack anything like SHA-256.”

This makes my brain hurt, and I’m not sure what makes you think we cannot crack SHA-2 hashes with this cluster.Bitcoin price nz we can crack SHA-256 at a rate of 21.4 G/s, and SHA-512 at a rate of 2.2 G/s. We can also crack SHA-3 at a rate of 2.2 G/s. If it is still not obvious to you, those are insanely fast speeds.

Please also understand that while SHA2 is a bit slower than some of the other crypto hash functions, it is still not sufficient for password storage.

> “all this shows is how insecure the windows hashes are and how a proper hash (such as SHA2 with a salt) wouldn’t have fallen so easily.”

No, it would have fallen just as easily. We can crack salted SHA2 at a rate of 21.4 G/s. While that is far from the 340+ G/s we can achieve with MD4, that’s still ridiculously fast. Again, not sure why the media focused on LM/NTLM, but we do much more than that at highly accelerated rates.

I am also concerned that you feel salted SHA2 is a proper means of storing passwords.Bitcoin price nz let me set the record straight: no cryptographic hash algorithm — salted or unsalted — is sufficient for password storage. It does not matter if you are using MD4, MD5, SHA1, SHA2, or SHA3 — they are all equally bad. You must only store passwords using an algorithm specifically designed for password storage, such as scrypt, pbkdf2, or any modern crypt(3) algorithm including bcrypt and sha512crypt.

> “that is a real purdy computer and all.. But NTLM? He might as well use it for benchmarking with wolfenstein 3D! Let me know when he breaks a simple 20 character AES256 password…remotely and w/o backend access.”

You seem to lack a fundamental understanding of the differences between encryption and hashing. We deal with hashes, not encryption. Passwords are (typically) not stored using reverisible encryption, but rather with hash algorithms which are one-way (non-reversible.) we are not breaking any encryption with this cluster.Bitcoin price nz

And again, we’ve benchmarked (and also actively crack) much more than just the two algorithms the media is focusing on.

Hope this makes things more clear for all. Thanks for your interest!

The coolest electronic toys you’ll see at NAMM 47 comments

More from this category recent comments

Rex on careful testing reveals USB cable duds

• max ward on making the case for slackware in 2018

Y knot on careful testing reveals USB cable duds

Wade on repairs you can print: 3D printing is for (solder) suckers

Jonathan on 3D print A 3D printer frame

Ǝıuuɐ on careful testing reveals USB cable duds

DW on repairs you can print: 3D printing is for (solder) suckers

• dainbramage on here’s why hoverboard motors might belong in robots

Y knot on start your apollo collection with an open source DSKY

Zosh on careful testing reveals USB cable duds

bitcoin price nz

Now on hackaday.Io

• lutetium has added deus as a contributor to hack chat.

• marko liked nrf51822 BLE flex module.

• thomas wrote a reply on eforth for cheap STM8S gadgets.

• patrick wrote a reply on project log new firmware release: version 1.2.0-dev.

• patrick wrote a comment on project log new firmware release: version 1.2.0-dev.

• frank buss wrote a reply on circuit python hack chat.

• hoerlemann liked farmbot – open-source CNC farming.

• lutetium has added ved@prakash as a contributor to hack chat.

• istiak ahmed wrote a comment on project log PIR motion detector BISS0001.

• agp.Cooper wrote a comment on PIR amplifier and hack.