Sunday, April 29, 2012

New builds - 1.31a, with GTX680 support!

Good news, everybody!  The Cryptohaze downloads have gotten BIGGER!

And there's another release.  1.31a.

I've (theoretically) fixed a missing DLL in the Windows build, and I've added GTX680 (sm_30) support for the Windows and Linux builds.  If anyone actually has a GTX680 in a Mac, let me know and I'll make a build...

Also, I've not actually tested this on a GTX680.  If you have one, can you please verify that everything works?  Thanks!

libcurl linking errors on Windows?

Are you getting libcurl link errors on Windows that look like this?

unresolved external symbol __imp__curl_easy_cleanup 
unresolved external symbol __imp__curl_easy_perform 
unresolved external symbol __imp__curl_easy_setopt
unresolved external symbol __imp__curl_easy_init

Fear no more!  First, ensure you are linking against the correct libraries, which should include:
libcurl.lib ws2_32.lib winmm.lib wldap32.lib

If this doesn't fix it, you probably need to add an additional Preprocessor Definition: CURL_STATICLIB - and it should fix the issue!  Hopefully this saves someone some time.

Tuesday, April 24, 2012

Cryptohaze tools 1.31 out - CUDA 4.2 release

New release.

1.31, with CUDA 4.2 compatibility and a few minor tweaks to work around a bug I found in 1.30 that involved some hashes not being found.

It also includes the IP address brute forcing script in the charsets/ip_addresses directory (for Unix - please, if anyone wants to make a Windows batch file, I'd really appreciate it!)

Go grab it & let me know if you have any problems.

Monday, April 23, 2012

Brute forcing IP address with the Cryptohaze Multiforcer

A few weeks ago, phillips321 had a problem.  He wanted to brute force IP addresses.  There was no good tool out there to do this, and brute forcing 4B+ MD5s is a bit slow on a CPU.

So, he wrote a quick dictionary and used Hashcat to crack the IPs.  And, as a good security consultant should do, blogged about it:

I replied that the per-position charsets with the Cryptohaze Multiforcer could do much the same, and then promptly forgot about it until now.

One significant flaw in his approach is that some systems will store IP addresses as "", and some will store them as "" - it depends on what type of odd hardware you're bothering.

If you don't care about brute forcing hashes of IP addresses, you can probably go somewhere else now.  Otherwise, onward!