hashcat Forum - Old oclHashcat Announcements

oclHashcat v2.00

Fri, 04 Dec 2015 16:03:45 +0000

Download here: https://hashcat.net/oclhashcat/

This oclHashcat version 2.00 is all about Open-Source. Yes, you read it right. We went Open-Source!

If you want to read more about the background of this, you can find the details here: https://hashcat.net/forum/thread-4880.html

Beside that, there's also alot of changes from the previous version 1.37 to this version.

Most important changes

Bitsliced GPU kernel of the DES based algorithms LM and DEScrypt
TrueCrypt cracker is now full-featured
Removed Timebomb-, Beta- and Keyfile- checks
Added support for all AMD Fiji based GPU (Fury)

Newly added algorithms

Blockchain, My Wallet
MS-AzureSync PBKDF2-HMAC-SHA256

Bitsliced GPU kernel

Bitsliced DES code was an important thing to add, many people were looking for this feature for a long time. If you want to know more about the details of how the implementation went you can read about the details here: https://hashcat.net/forum/thread-4761.html

But to shortcut it, the status is that -m 1500 (DEScrypt) and -m 3000 (LM) now both use bitsliced code for Brute-Forced attacks. Two more things will be done soon:

Support for bitsliced Oracle-DES and RACF
Support for hardcoded salt in DEScrypt

Once we finish the hardcoded salt in DEScrypt we can expect even more performance.

Make sure to monitor oclHashcat's GitHub repository if you're interested in this.

TrueCrypt cracker

The previous release version of oclHashcat (v1.37) was already able to crack TrueCrypt volumes, though it only is able to crack AES encrypted volumes.

With oclHashcat v2.00 we added the following functionality:

Crack Serpent
Crack Twofish
Crack cascaded ciphers
Crack keyfile-protected volumes

That means we finally have a full-featured TrueCrypt cracking engine. It supports all hashes, ciphers, cascades, keyfiles, hidden-volumes, bootable-devices in any possible combination.

But beside that, we also found a way to speed up TrueCrypt cracking massively!

If you're interested in this, please read my post "Cracking eight different TrueCrypt ciphers for the price of three": https://hashcat.net/forum/thread-4812.html

ATM, oclHashcat is the only cracker able to perform this attack.

Full changelog v1.37 -> v2.00

Quote:
Type: Project
File: All
Desc: Made the project Open-Source

Type: Project
File: All
Desc: Switched the license to MIT

Type: Feature
File: Host
Desc: Removed Timebomb-, Beta- and Keyfile- checks

Type: Driver
File: Host
Desc: Added support for AMD APP SDK v3.0 GA

Type: Driver
File: Host
Desc: Added support for AMD ADL 8.0

Type: Driver
File: Host
Desc: added support for NV CUDA 7.5

Type: Feature
File: Host
Desc: Replaced support for NVAPI with support for its successor GDK, starting with version 352.55

Type: Driver
File: Host
Desc: Added support for all AMD Fiji based GPU (Fury)
Trac: 677

Type: Change
File: Kernel
Desc: Bitsliced mode -m 1500 = crypt, DES(Unix), Traditional DES in mask mode

Type: Change
File: Kernel
Desc: Bitsliced mode -m 3000 = LM in mask mode

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12700 = Blockchain, My Wallet
Trac: 645

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12800 = MS-AzureSync PBKDF2-HMAC-SHA256
Trac: 669

Type: Feature
File: Kernel
Desc: Added new hash mode -m 6211 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + XTS 512 bit
Desc: Added new hash mode -m 6212 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + XTS 1024 bit
Desc: Added new hash mode -m 6213 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + XTS 1536 bit
Desc: Added new hash mode -m 6221 = TrueCrypt 5.0+ PBKDF2-HMAC-SHA512 + XTS 512 bit
Desc: Added new hash mode -m 6222 = TrueCrypt 5.0+ PBKDF2-HMAC-SHA512 + XTS 1024 bit
Desc: Added new hash mode -m 6223 = TrueCrypt 5.0+ PBKDF2-HMAC-SHA512 + XTS 1536 bit
Desc: Added new hash mode -m 6231 = TrueCrypt 5.0+ PBKDF2-HMAC-Whirlpool + XTS 512 bit
Desc: Added new hash mode -m 6232 = TrueCrypt 5.0+ PBKDF2-HMAC-Whirlpool + XTS 1024 bit
Desc: Added new hash mode -m 6233 = TrueCrypt 5.0+ PBKDF2-HMAC-Whirlpool + XTS 1536 bit
Desc: Added new hash mode -m 6241 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + XTS 512 bit + boot-mode
Desc: Added new hash mode -m 6242 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + XTS 1024 bit + boot-mode
Desc: Added new hash mode -m 6243 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + XTS 1536 bit + boot-mode
Trac: 394

Type: Feature
File: Kernel
Desc: Added support for keyfiles with TrueCrypt 5.0+ for all modes
Trac: 618

Type: Feature
File: Host
Desc: Added new status-display line showing Recovered/Time rate for current and average activity

Type: Change
File: Kernel
Desc: Hash-Modes 10900, 11900, 12000 and 12100 switched salt encoding from raw to base64
Trac: #658

Type: Change
File: Host
Desc: Fine-tuned fanspeed regulation to work nice even on bigger systems (6+ GPU)

Type: Change
File: Host
Desc: Renamed rule 'x' to 'O', omit X chars of word at pos N

Type: Change
File: Host
Desc: Added rule 'x', extract X chars of word at pos N, to keep compatibility to JtR/crack

Type: Change
File: Host
Desc: Switched to newer glibc for binaries (testphase; please contact us if you have problems)

Type: Bug
File: Host
Desc: On Nvidia, do not use cuMemAllocHost() on CUDA systems with many GPUs to avoid errors of type cuMemAllocHost() 999

Type: Bug
File: Host
Desc: On Nvidia, make sure to clean constant buffer for each iteration of maskfiles
Trac: 691

Type: Bug
File: Host
Desc: When trying to crack a raw hash with appended salt, the salt length was taken into account when calculating the number of bytes for the innerloop

--
atom

oclHashcat v1.37

Tue, 18 Aug 2015 16:09:14 +0000

Download here: https://hashcat.net/oclhashcat/

This oclHashcat version 1.37 is about driver compatibility and packaging but also on performance increase and new algorithms.

Most important changes

AMD binary kernel format change enables oclHashcat to let the user select any catalyst driver version he wants, back to v14.9
NV binary kernel format change massively reduced disk usage, from 3236mb down to 894mb (includes newly added kernels)
Performance increases

Performance increases

We're very proud especially on the sha512crypt speed increase. You will also notice some multihash performance increase and a much smaller memory footprint because we fixed some memory leaks.

There's a small drop on the performance for MD4/MD5/NTLM. This is a trade-off. The performance drop affects only Brute-Force, but therefore we gain 15% performance increase on rule-based attacks for all those very fast algorithms.

Full performance changelog v1.36 -> v1.37

https://docs.google.com/spreadsheets/d/1...sp=sharing

Most important algorithms added

eCryptfs
Oracle T: Type (Oracle 12+)
RAR3 (with encrypted header)

We also added some PBKDF2-HMAC-* generic hashes because of the strong request on this. Note that the RAR3 kernel only supports archives with encrypted headers yet. In a later version we will add support for RAR3 without encrypted headers and RAR5, too.

Full changelog v1.36 -> v1.37

Quote:
Type: Driver
File: Host
Desc: Added support for all AMD Catalyst >= v14.9

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11700 = GOST R 34.11-2012 (Streebog) 256-bit

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11800 = GOST R 34.11-2012 (Streebog) 512-bit

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11900 = PBKDF2-HMAC-MD5

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12000 = PBKDF2-HMAC-SHA1

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12100 = PBKDF2-HMAC-SHA512

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12200 = eCryptfs

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12300 = Oracle T: Type (Oracle 12+)

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12400 = BSDiCrypt, Extended DES

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12500 = RAR3-hp

Type: Feature
File: Kernel
Desc: Added new hash mode -m 12600 = ColdFusion 10+

Type: Feature
File: Kernel
Desc: Added support for longer field lengths in -m 11400 = SIP digest authentication (MD5)
Trac: #539, #624

Type: Feature
File: Host
Desc: Fixed digest size for all hash-types internally to 128 bit

Type: Feature
File: Host
Desc: Fixed a bug in .hcmask file custom charset keyspace
Trac: #617

Type: Change
File: Kernel
Desc: Renamed -m 112 = Oracle 11g/12c to -m 112 = Oracle S: Type (Oracle 11+)

Type: Change
File: Kernel
Desc: Renamed -m 3100 = Oracle 7-10g, DES(Oracle) to -m 3100 = Oracle H: Type (Oracle 7+)

Type: Change
File: Host
Desc: Renamed -m 3800 = md5 ($pass.$salt.$pass) to -m 3800 = md5 ($salt.$pass.$salt)

Type: Change
File: Host
Desc: Renamed -m 1100 = Domain Cached Credentials, mscash to -m 1100 = Domain Cached Credentials (DCC), MS Cache

Type: Change
File: Host
Desc: Renamed -m 2100 = Domain Cached Credentials2, mscash2 to -m 2100 = Domain Cached Credentials 2 (DCC2), MS Cache 2

Type: Change
File: Host
Desc: Reordered hash-type listing in usage screen and set default benchmark ordering anlogue to that listing

Type: Change
File: Host
Desc: oclHashcat binaries are now being build on Ubuntu 15.04 (vivid)

Type: Bug
File: Host
Desc: Loopback file names now also depend and the path contains a random number, not timestamp only

Type: Bug
File: Host
Desc: Fixed a bug where the extra rules -j and -k were applied based on the wordlist-size not position

Type: Bug
File: Host
Desc: Fixed problem with --loopback that could sometimes lead to an infinite loop on windows
Trac: #626

--
atom

oclHashcat v1.36

Sat, 25 Apr 2015 17:36:13 +0000

Download is here: https://hashcat.net/oclhashcat/

This version 1.36 is a wild mix of nice updates

Still, all oclHashcat versions back to 1.33 share the same driver dependencies for AMD. If you have a running oclHashcat v1.33 or newer then v1.36 will work, too, without a driver update.

Most important changes:

Added new hash mode -m 11300 = Bitcoin/Litecoin wallet.dat
Added new hash mode -m 11600 = 7-Zip
Fixed a bug in NVidia multihash kernels: MD5, NTLM, IPB2
The parameters --show / --left do work with both halves of LM hashes (if they were 32 hex chars long)
Optimized final round flushing (reduces time at last percents of progress with slower speed)
Optimized rejection handling (for example passwords > 8 if cracking DEScrypt or < 8 if cracking WPA/WPA2, etc)
The speed in status display is no longer divide by the number of uncracked salts

Don't forget to visit the new FAQ pages, it's worth a read: https://hashcat.net/wiki/doku.php?id=fre..._questions

Full changelog v1.35 -> v1.36

Quote:
Type: Driver
File: Kernel
Desc: Added support for NV ForceWare 346.59 driver

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11400 = SIP digest authentication (MD5)
Trac: #539

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11300 = Bitcoin/Litecoin wallet.dat
Trac: #434

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11500 = CRC32
Trac: #532

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11600 = 7-Zip
Trac: #532

Type: Feature
File: Host
Desc: Optimized final round flushing (reduces time at last percents of progress with slower speed)

Type: Feature
File: Host
Desc: Optimized rejection handling (for example passwords > 8 if cracking DEScrypt etc)

Type: Feature
File: Host
Desc: Added parameter --bitmap-min to help loading huge hashlists faster

Type: Feature
File: Host
Desc: In status display, if a single hash is longer than 40 chars, truncate it and add "..." to it

Type: Change
File: Host
Desc: Renamed -m 3810 = md5($salt.$pass.$salt) to -m 3800 = md5($salt.$pass.$salt)

Type: Change
File: Host
Desc: Renamed -m 4710 = sha1($salt.$pass.$salt) to -m 4900 = sha1($salt.$pass.$salt)

Type: Change
File: Host
Desc: The speed in status display is no longer divide by the number of uncracked salts

Type: Change
File: Host
Desc: If all hashes bound to a salt are cracked, reduce the progress count of one salt from the total progress

Type: Change
File: Host
Desc: --show/--left does now work with both halves of -m 3000 = LM hashes if they are 32 hex chars long
Trac: #448

Type: Bug
File: Kernels
Desc: Fixed a bug in NVidia multihash kernels: MD5, NTLM, IPB2

Type: Bug
File: Host
Desc: Added additional checks for hexadecimal values supplied in masks by using the --hex-charset switch
Trac: 610

Type: Bug
File: Host
Desc: Fixed a bug in NVidia workload balancing

Type: Bug
File: Host
Desc: Fixed a bug in single rule applied to each word from left dict

Type: Bug
File: Host
Desc: Problem with "," character escaping in .hcmask file fixed

Type: Bug
File: Host
Desc: Fixed a bug in -m 101, was showing a wrong cracked plaintext

oclHashcat v1.35

Sun, 22 Mar 2015 02:07:25 +0000

Download here: https://hashcat.net/oclhashcat/

This version 1.35 is about performance increase and bug fixes. Even if you did not face any errors with v1.33 we recommend upgrading.

Good thing is both oclHashcat v1.35 and oclHashcat v1.33 share the same driver dependancies. If you had a running v1.33 then v1.35 will work, too.

Most important changes:

Increased speed for SHA1 raw kernels, all AMD GPU
Increased speed for PDF kernel, all NVidia GPU
Increased speed for all multihash kernel using a different bitmap technique, all GPU
Fixed a race condition in multihash kernels
Fixed a buffer overflow that could lead to all kinds of segmentation fault or system freezing
Fixed a bug which caused clCreateBuffer() -61 Error even on single hashes

Full changelog v1.34 -> v1.35

Quote:
Type: Feature
File: Kernel
Desc: Increased speed for all multihash kernel using a bitmap technique

Type: Bug
File: Kernels
Desc: Fixed a bug in NVidia multihash kernels that a hash was not found even with the correct plain

Full changelog v1.33 -> v1.34

Quote:
Type: Feature
File: Kernel
Desc: Increased speed for SHA1 raw kernels (-m 100/110/120/130/140) on GCN cards (7970, 280x, 290x, ...)

Type: Feature
File: Kernel
Desc: Increased speed for PDF kernel (-m 104xx and -m 105xx) for all NVidia GPU

Type: Feature
File: Kernel
Desc: Increased speed for all multihash kernel using a different bitmap technique

Type: Feature
File: Kernel
Desc: Added oclHashcat compile timestamp to buffered binary kernels to avoid collisions with older versions

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11000 = PrestaShop
Trac: #589

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11100 = PostgreSQL Challenge-Response Authentication (MD5)
Trac: #490

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11200 = MySQL Challenge-Response Authentication (SHA1)
Trac: #490

Type: Feature
File: Kernel
Desc: Added support for 32 bytes ID objects for hash type -m 10500 = PDF 1.4 - 1.6
Trac: #594

Type: Feature
File: Host
Desc: Inform user with small wordlists how to avoid slow speed with slow hashes
Trac: #597

Type: Change
File: Host
Desc: Renamed -m 7100 = OS X v10.8 / v10.9 to OS X v10.8+

Type: Workaround
File: Host
Desc: New workaround for -m 2500 = WPA/WPA2 key versions which are not valid (should always be < 256)

Type: Bug
File: Kernels
Desc: Fixed a race condition in multihash kernels

Type: Bug
File: Kernels
Desc: Fixed a buffer overflow that could lead to all kinds of segmentation fault or system freezing
Trac: #591

Type: Bug
File: Host
Desc: The key size (AES 128 vs AES 256) for office 2007 hashes was not shown correctly in output/status
Trac: #590

Type: Bug
File: Host
Desc: Fixed a bug if a rule in -j changes the length of the words in the wordlist, ex. ]
Trac: #593

Type: Bug
File: Host
Desc: Fixed a crash when using the outfile remove feature together with some hash types
Trac: #593

Type: Bug
File: Host
Desc: Fixed a problem where wrong restore point percentage was shown
Trac: #606

Type: Bug
File: Host
Desc: Fixed a buffer overflow in stdin mode

Type: Bug
File: Host
Desc: Fixed a bug which caused clCreateBuffer() -61 Error even on single hashes

Type: Bug
File: Host
Desc: Fixed a bug which caused clEnqueueCopyBuffer() -30 Error by limiting --gpu-loops to a maximum of 1024

Type: Bug
File: Host
Desc: Fixed a bug related to the maximum password length supported per hash-type

--
atom

oclHashcat v1.34

Sat, 21 Mar 2015 16:12:03 +0000

Download here: https://hashcat.net/oclhashcat/

This version 1.34 is about performance increase and bug fixes. Even if you did not face any errors with v1.33 we recommend upgrading.

Good thing is both oclHashcat v1.34 and oclHashcat v1.33 share the same driver dependancies. If you had a running v1.33 then v1.34 will work, too.

Most important changes:

Increased speed for SHA1 raw kernels, all AMD GPU
Increased speed for PDF kernel, all NVidia GPU
Increased speed for all multihash kernel using a different bitmap technique, all GPU
Fixed a race condition in multihash kernels
Fixed a buffer overflow that could lead to all kinds of segmentation fault or system freezing
Fixed a bug which caused clCreateBuffer() -61 Error even on single hashes

Full changelog v1.33 -> v1.34

Quote:
Type: Feature
File: Kernel
Desc: Increased speed for SHA1 raw kernels (-m 100/110/120/130/140) on GCN cards (7970, 280x, 290x, ...)

Type: Feature
File: Kernel
Desc: Increased speed for PDF kernel (-m 104xx and -m 105xx) for all NVidia GPU

Type: Feature
File: Kernel
Desc: Increased speed for all multihash kernel using a different bitmap technique

Type: Feature
File: Kernel
Desc: Added oclHashcat compile timestamp to buffered binary kernels to avoid collisions with older versions

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11000 = PrestaShop
Trac: #589

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11100 = PostgreSQL Challenge-Response Authentication (MD5)
Trac: #490

Type: Feature
File: Kernel
Desc: Added new hash mode -m 11200 = MySQL Challenge-Response Authentication (SHA1)
Trac: #490

Type: Feature
File: Kernel
Desc: Added support for 32 bytes ID objects for hash type -m 10500 = PDF 1.4 - 1.6
Trac: #594

Type: Feature
File: Host
Desc: Inform user with small wordlists how to avoid slow speed with slow hashes
Trac: #597

Type: Change
File: Host
Desc: Renamed -m 7100 = OS X v10.8 / v10.9 to OS X v10.8+

Type: Workaround
File: Host
Desc: New workaround for -m 2500 = WPA/WPA2 key versions which are not valid (should always be < 256)

Type: Bug
File: Kernels
Desc: Fixed a race condition in multihash kernels

Type: Bug
File: Kernels
Desc: Fixed a buffer overflow that could lead to all kinds of segmentation fault or system freezing
Trac: #591

Type: Bug
File: Host
Desc: The key size (AES 128 vs AES 256) for office 2007 hashes was not shown correctly in output/status
Trac: #590

Type: Bug
File: Host
Desc: Fixed a bug if a rule in -j changes the length of the words in the wordlist, ex. ]
Trac: #593

Type: Bug
File: Host
Desc: Fixed a crash when using the outfile remove feature together with some hash types
Trac: #593

Type: Bug
File: Host
Desc: Fixed a problem where wrong restore point percentage was shown
Trac: #606

Type: Bug
File: Host
Desc: Fixed a buffer overflow in stdin mode

Type: Bug
File: Host
Desc: Fixed a bug which caused clCreateBuffer() -61 Error even on single hashes

Type: Bug
File: Host
Desc: Fixed a bug which caused clEnqueueCopyBuffer() -30 Error by limiting --gpu-loops to a maximum of 1024

Type: Bug
File: Host
Desc: Fixed a bug related to the maximum password length supported per hash-type

--
atom

oclHashcat v1.33

Mon, 16 Feb 2015 19:30:40 +0000

Download here: https://hashcat.net/oclhashcat/

This version 1.33 is the finalized version of what v1.32 should have been.

There's not much to see from the changelog but there was a ton of changes in the inner working which make this release is really a good one.

Most important changes:

Support for cracking password protected PDF documents
Added a raw PBKDF2 kernel
A total of 150 algorithms is supported now
Multithreaded wordlist loading

Full changelog v1.32 -> v1.33

Quote:
Type: Feature
File: Kernel
Desc: added new hash mode -m 10400 = PDF 1.1 - 1.3 (Acrobat 2 - 4)
Trac: #160

Type: Feature
File: Kernel
Desc: added new hash mode -m 10410 = PDF 1.1 - 1.3 (Acrobat 2 - 4) + collider-mode #1
Trac: #160

Type: Feature
File: Kernel
Desc: added new hash mode -m 10420 = PDF 1.1 - 1.3 (Acrobat 2 - 4) + collider-mode #2
Trac: #160

Type: Feature
File: Kernel
Desc: added new hash mode -m 10500 = PDF 1.4 - 1.6 (Acrobat 5 - 8)
Trac: #160

Type: Feature
File: Kernel
Desc: added new hash mode -m 10600 = PDF 1.7 Level 3 (Acrobat 9)
Trac: #160

Type: Feature
File: Kernel
Desc: added new hash mode -m 10700 = PDF 1.7 Level 8 (Acrobat 10 - 11)
Trac: #160

Type: Feature
File: Kernel
Desc: added new hash mode -m 10900 = PBKDF2-HMAC-SHA256
Trac: #256

Type: Feature
File: Kernel
Desc: added support for cracking AES-256 in -m 9400 = Office 2007
Trac: #576

Type: Feature
File: Host
Desc: Multithreaded wordlist loader

Type: Feature
File: Host
Desc: Added last restore point information to status screen
Trac: #445

Type: Feature
File: Host
Desc: Support added to allow both {SSHA} and {ssha} signatures for -m 111 = nsldaps, SSHA-1(Base64), Netscape LDAP SSHA
Trac: #537

Type: Feature
File: Host
Desc: Avoid using GPU_NUM_COMPUTE_RINGS to solve clGetDeviceIDs() -1 on some systems
Trac: #564

Type: Bug
File: Host
Desc: Beta key date check will now be disabled in release versions
Trac: #536

Type: Bug
File: Host
Desc: Minor change in exit code handling, priority of exit codes changed
Trac: #545

Type: Bug
File: Host
Desc: Solved a memory problem when using --show and --username with corrupted or missing user name
Trac: #565

Type: Bug
File: Host
Desc: Fixed a formatting problem when using the --username switch while cracking (colons were wrongly prepended to each line)
Trac: #566

--
atom

oclHashcat v1.32

Thu, 15 Jan 2015 15:38:36 +0000

Download here: https://hashcat.net/oclhashcat/

This version 1.32 is a preponed release due to many conflicts between v1.31 and the latest AMD and NV drivers.

It does not include support for PDF as we're not yet finished implementing all different versions of PDF. PDF will be supported in next version of oclHashcat.

Still, there's a lot of other stuff that comes with this release. The most important:

Workaround a bug which is caused by AMD Catalyst 14.9 driver that could lead to uncracked office documents
Mark AMD Catalyst 14.12 as entirely broken for OpenCL and show a warning message on startup
Support ForceWare 346.x to solve cuModuleLoad() 209 error -- Make sure you have 346.x installed !!!
Add support for Tesla K80 devices (sm_37) to solve cuModuleLoad() 301 error
New AMP kernels to compute passwords candidates for slow hashes on GPU as well
Increased scrypt performance

Full changelog v1.31 -> v1.32

Quote:
Type: Driver
File: Host
Desc: Marked AMD Catalyst 14.12 as broken driver

Type: Driver
File: Kernel
Desc: Added support for AMD APP SDK v3.0 beta

Type: Driver
File: Kernel
Desc: Added support for NV ForceWare 346.29 driver

Type: Driver
File: Host
Desc: added support for NV CUDA 7.0

Type: Driver
File: Kernel
Desc: Added support for NV new GPUs: "sm_37", used in Tesla K80

Type: Driver
File: Host
Desc: NVidia dropped support for CUDA enabled cards <= sm_13

Type: Driver
File: Host
Desc: Removed bzero kernel as they are now supported by native runtime

Type: Workaround
File: Kernel
Desc: Fixed bug in RC4 based algorithms like Office initiated by AMD drivers

Type: Reimplementation
File: Kernel and Host
Desc: Rewrote slow hash candidate amplifiers, ported from CPU to GPU

Type: Reimplementation
File: Kernel
Desc: Rewrote support for algorithm -m 8900 = scrypt, simply more speed
Trac: #507

Type: Feature
File: Kernel
Desc: added support for TrueCrypt 5.x containers in all hash modes -m 62XX

Type: Feature
File: Kernel
Desc: added new hash mode -m 4710 = sha1($salt.$pass.$salt)
Trac: #517

Type: Feature
File: Kernel
Desc: added new hash mode -m 10200 = Cram MD5
Trac: #528

Type: Feature
File: Kernel
Desc: added new hash mode -m 10300 = SAP CODVN H (PWDSALTEDHASH) iSSHA-1

Type: Feature
File: Kernel
Desc: added new hash mode -m 10800 = SHA384

Type: Change
File: Host
Desc: renamed -m 123 = Django (SHA-1) to -m 124 = Django (SHA-1)

Type: Change
File: Host
Desc: renamed --powertune-disable to --powertune-enable and set default to unset

Type: Feature
File: Host
Desc: Added parameter --scrypt-tmto to manually override automatically calculated tmto settings

Type: Bug
File: Host
Desc: fixed a bug when two rules in chaining-mode exceed maximum 15 functions calls in sum

Type: Bug
File: Host
Desc: fixed a bug in -j if the rule causes to change password length

Type: Bug
File: Host
Desc: fixed problem with ADL fan speed display, catalyst 14.9 driver had problems querying the fan information/speed
Trac: #514

Type: Bug
File: Host
Desc: fixed a problem with too aggressive plain rejection check
Trac: #515

Type: Bug
File: Host
Desc: show error message when the user attempts to use directories in combinator attack (which is not supported)
Trac: #518

Type: Bug
File: Host
Desc: show error message when the user tries to use too long masks, fixes a crash
Trac: #522

Type: Bug
File: Host
Desc: Fixed Redmine format; support for 32 bytes of hexadecimal salt added
Trac: #543

Type: Bug
File: Host
Desc: Fixed a problem when using --remove with a multi-hccap file
Trac: #552

type: Feature
file: Rules
desc: added dive.rule
Trac: #519

--
atom

oclHashcat v1.31

Thu, 02 Oct 2014 19:22:07 +0000

Download here: https://hashcat.net/oclhashcat/

oclHashcat v1.31 is the first oclHashcat version that fully supports the new Maxwell v2 GPUs from NVidia (GTX 970/980). There are a lot of request coming in about oclHashcat support for those cards as they are kind of special. If you want to know more about that, please read this:

Therefore we decided to release the 1.31 version a bit sooner as the usual update frequency.

We spend a lot of time (as always) in finding new optimizations and performance gains and it seems that it was worth the effort, see for instance the direct comparison of v1.20 and v1.31 for NVidia GTX Titan: http://hashcat.net/forum/thread-3707.html

Furthermore, we've added support and optimized the kernels for AMD Catalyst 14.9 and NV ForceWare 343.22. Therefore it is required that you use that specific version of catalyst or ForceWare together with oclHashcat 1.31.

New Algorithms:

Office 2003 / 2007 / 2010 / 2013 documents
Cisco $8$ (PBKDF2-SHA256) and $9$ (scrypt)
Juniper IVE
SipHash
Django (PBKDF2-SHA256)
RAdmin2
md5($salt.$pass.$salt)
md5(strtoupper(md5($pass)))

We think the addition of Office 97/2003 algorithm is the most interesting one, at least from a forensics and pentesters perspective. For this hash-type, there's two ways (and hash types) to crack Office 97/2003 documents. That is either by searching for all collisions (see -m 9710/9720 and -m 9810/9820) or with the -m 9700/9800 "conventional" method. oclHashcat 1.31 supports all Office document types. For example it is not limited to doc/docx, it will work also on Microsoft Excel .xmlx, .pptx files etc.

The new -m 9720 and -m 9820 mode will help you to find all "passwords" and they do not stop after the first crack. That's important if you want to know "all" matching passwords in case you're looking for a password you can use to test for password re-use. For more details about the addition of Office 97/2003 see http://hashcat.net/forum/thread-3665.html

As far as we know, oclHashcat is the first cracker to support cracking of the new Cisco hashing schemes (PBKDF2-SHA256 and scrypt) and the Juniper IVE hashes.

Full changelog v1.30 -> v1.31

Quote:
Type: Driver
File: Host
Desc: added support for AMD Catalyst 14.9

Type: Driver
File: Host
Desc: added support for NV CUDA 6.5

Type: Driver
File: Kernel
Desc: Added support for NV new GPUs: "sm_52" (Maxwell v2), used in GTX 970/980

Type: Feature
File: Kernel
Desc: added new hash mode -m 12 = PostgreSQL

Type: Feature
File: Kernel
Desc: added new hash mode -m 123 = Django (SHA-1)

Type: Feature
File: Kernel
Desc: added new hash mode -m 501 = Juniper IVE

Type: Feature
File: Kernel
Desc: added new hash mode -m 4300 = md5(strtoupper(md5($pass)))

Type: Feature
File: Kernel
Desc: added new hash mode -m 3810 = md5($salt.$pass.$salt)

Type: Feature
File: Kernel
Desc: added new hash mode -m 9200 = Cisco $8$

Type: Feature
File: Kernel
Desc: added new hash mode -m 9300 = Cisco $9$

Type: Feature
File: Kernel
Desc: added new hash mode -m 9400 = Office 2007

Type: Feature
File: Kernel
Desc: added new hash mode -m 9500 = Office 2010

Type: Feature
File: Kernel
Desc: added new hash mode -m 9600 = Office 2013

Type: Feature
File: Kernel
Desc: added new hash mode -m 9700 = MS Office <= 2003 MD5 + RC4, oldoffice$0, oldoffice$1

Type: Feature
File: Kernel
Desc: added new hash mode -m 9710 = MS Office <= 2003 MD5 + RC4, collider-mode #1

Type: Feature
File: Kernel
Desc: added new hash mode -m 9720 = MS Office <= 2003 MD5 + RC4, collider-mode #2

Type: Feature
File: Kernel
Desc: added new hash mode -m 9800 = MS Office <= 2003 SHA1 + RC4, oldoffice$3, oldoffice$4

Type: Feature
File: Kernel
Desc: added new hash mode -m 9810 = MS Office <= 2003 SHA1 + RC4, collider-mode #1

Type: Feature
File: Kernel
Desc: added new hash mode -m 9820 = MS Office <= 2003 SHA1 + RC4, collider-mode #2

Type: Feature
File: Kernel
Desc: added new hash mode -m 9900 = Radmin2

Type: Feature
File: Kernel
Desc: added new hash mode -m 10000 = Django (PBKDF2-SHA256)
Trac: #473

Type: Feature
File: Kernel
Desc: added new hash mode -m 10100 = SipHash
Trac: #509

Type: Feature
File: Host
Desc: new feature to notice the user how many hashes were removed because of pot file remove feature
Trac: #506

Type: Feature
File: Host
Desc: output the MAC address (BSSID) too when cracking WPA/WPA2, pot file output is different too
Trac: #440

Type: Change
File: Host
Desc: Renamed -m 8800 = Android FDE to -m 8800 Android FDE <= 4.3

Type: Change
File: Docs
Desc: Removed docs/credits.txt

Type: Bug
File: Host
Desc: fixed problem with ADL fan speed information; only happening on some non-reference design Overdrive6 GPUs
Trac: #498

Type: Bug
File: Host
Desc: fixed crash with --debug-mode=x when number of rules was exactly 14 (approaching maximum amount of rules allowed)
Trac: #505

Type: Bug
File: Host
Desc: fixed inconsistency when using --show together with --username and different --outfile-format options
Trac: #513

oclHashcat v1.30

Thu, 21 Aug 2014 15:48:44 +0000

Download here: https://hashcat.net/oclhashcat/

This release is again focused on performance increase of the kernels and bugfixes. However, the most code intensive change in this version was the new workload dispatcher as it's part of the the oclHashcat core. The old one wasn't that bad, but the new one is simply faster which adds up to the increased performance of the kernels.

As always, make sure to unpack into a new folder. Never reuse an existing oclHashcat folder (because of the cached kernels).

One important thing for AMD users: You will need to update to the latest beta version of catalyst before updating oclHashcat. We've decided to no longer wait for AMD to ship the latest "stable" catalyst driver simply because they aren't any more stable than beta drivers...

There's also one change made to the binaries itself. We now are using our own toolchain (thanks to crosstool-ng) to create our own binaries with an older glibc. That was required to make the binaries compatible to linux distributions using an older glibc. That means you should be able to run cudaHashcat and oclHashcat now without glibc patching on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali), some (older) Debian systems, CentOS 6.4, etc..

New algorithms

Skype
Peoplesoft
md5($salt.md5($pass))
Mediawiki B type
Kerberos 5 AS-REQ Pre-Auth etype 23 as fast algorithm (reimplementation)
Android FDE
scrypt
Password Safe v2
Lotus Notes/Domino 8

Skype and Peoplesoft are just new parsers as you were already able to crack them with older oclHashcat versions by using the generic hashtypes and by formating the hashes in a way that oclHashcat can load them. By adding parsers we just make it more comfortable for the users to load the hashes as you can use them in their native output.

The md5($salt.md5($pass)) generic algorithm was simply added as it was required for the Mediawiki B type hash-type. It's a simple scheme that does not require any special comment.

The Kerberos 5 algorithm is a reimplementation as fast algorithm type. That is the case if an algorithm is fast enough to require an on-gpu candidate generator. The algorithm actually was fast enough and just by not selecting it as fast hash it lost some performance. By switching it to a fast type we got some speedup for free.

Now it gets interessing. The Android FDE algorithm that was added is the one that is using PBKDF2-HMAC-SHA1 + CBC-ESSIV-AES with 2000 iterations. Only tricky part was the "detection" of a filesystem. Note that this algorithm isn't used anymore in newer android devices. The new one uses scrypt instead of PBKDF2. For details about how the algorithm is working see here: https://hashcat.net/forum/thread-2270.html

That's why we've added scrypt to GPU. And what should I tell, it's PITA. The goal of scrypt to run slow on GPU has been fulfilled. Just one note about that. The intention (if I understood currectly) was to make the computuation slow because the memory access is slow. Well that's not what made it slow actually. It's simply the lack of the total memory available on the card. Note that, to run fast with GPGPU, you have to run many tasks in parallel. That means that you have to allocate a huge amount of memory for each parallel task and this is what kills the gpu, not the access time. Also note that this scrypt variant is the real scrypt, not the minimal version that is used for litecoin. The litecoin version uses extreme low settings for N, r and p such that it is not required to work on global memory for all operations. We're using a fully functional scrypt in which you can set N, r and p dynamically. For the benchmark, we're using the defaults of 16k, 8, 1.

The Password Safe v2 was also very interessting. This algorithm actually runs slower than the current one used in Password Safe v3, which is also supported with hash-type 5200. On my AMD hd7970, the v2 version runs with 101 kH/s while the v3 version runs with 506.2 kH/s but I don't think it's too much of a problem. Both run slow enough and are salted.

Last algorithm that was added is Lotus Notes/Domino 8 which was discovered by our own philsmd. Therefore, oclHashcat v1.30 is world's first Lotus Notes/Domino 8 (H-hashes) cracker! For details about how the algorithm is working see here: https://hashcat.net/forum/thread-3550.html

Performance increase

We've added some very special GPU type specific instructions that gave the speed boost. This means the increase of the performance depends on the GPU type. Every GPU type required different changes. It's mostly those chipsets that make the differences in cracking speed, after subtracting the effect that the shader count and clock stepping has.

In other words: Lookup your chipset, then you can apply the percentage change on your current speed with oclHashcat v1.21:

For our Test we used (all stock clocked):

VLIW1: R9 290x
VLIW4: hd6990 (only 1st core)
VLIW5: hd5770

sm_50: gtx 750Ti
sm_21: gtx 560Ti
sm_20: gtx 580

AMD VLIW1 (R9 * and hd7* series, state of the art)

AMD VLIW4 (most of the hd6* series)

AMD VLIW5 (most of the hd5* series)

NVidia sm_50 (Maxwell chipset, ex: 750Ti, future state of the art)

NVidia sm_21 (Older vector chipset)

NVidia sm_20 (Older scalar chipset)

some of the algorithms became a bit slower. That is mostly because of driver changes that we were unable to compensate with more efficient code.

Here's the entire performance change table: https://hashcat.net/misc/p130_img/changes_v130.png

Full changelog v1.21 -> v1.30

Quote:
Type: Driver
File: Kernel
Desc: Added support for AMD Catalyst v14.6 and v14.7 (beta) driver

Type: Driver
File: Kernel
Desc: Added support for NV ForceWare 340.24 driver

Type: Driver
File: Host
Desc: added support for AMD ADL 7.0

Type: Reimplementation
File: Host
Desc: Rewrote dispatcher thread from scratch

Type: Reimplementation
File: Kernel
Desc: Rewrote support for algorithm -m 7500 = Kerberos 5 AS-REQ Pre-Auth etype 23 as fast algorithm

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 23 = Skype
Trac: #474

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 133 = PeopleSoft
Trac: #419

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 3710 = md5($salt.md5($pass))

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 3711 = Mediawiki B type
Trac: #410

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8800 = Android FDE

Type: Feature
File: Host
Desc: Added support for algorithm -m 8900 = scrypt
Trac: #295

Type: Feature
File: Host
Desc: Added support for algorithm -m 9000 = Password Safe v2

Type: Feature
File: Host
Desc: Added support for algorithm -m 9100 = Lotus Notes/Domino 8

Type: Feature
File: Host
Desc: Added support for --increment with attack-mode 6 and attack-mode 7
Trac: #450

Type: Change
File: Kernel
Desc: Renamed -m 112 = Oracle 11g to -m 112 = Oracle 11g/12c

Type: Change
File: Kernel
Desc: Renamed -m 5200 = Password Safe SHA256 to -m 5200 = Password Safe v3

Type: Change
File: Kernel
Desc: Renamed -m 5800 = Samsung Android Password/PIN to -m 5800 = Android PIN

Type: Bug
File: Kernel
Desc: fixed bug in warp kernels were zero-byte leading plains are incorrectly displayed
Trac: #428

Type: Bug
File: Kernel
Desc: fixed bug in SAP CODVN B (BCODE) misses correct password in rare cases
Trac: #495

Type: Bug
File: Kernel
Desc: Enforce maximum password length for -m 8500 = RACF
Trac: #431

Type: Bug
File: Kernel
Desc: Rule iNX = Insert character X at position N didn't allow to insert a character at the very end of the plain
Trac: #457

Type: Bug
File: Host
Desc: fixed bug in bitmap table leading to uncracked 64-bit based hashes if bitmap_size > 0xffff

Type: Bug
File: Host
Desc: Separator for -m 22 = Juniper Netscreen/SSG (ScreenOS) should always be ':', regardless of --separator
Trac: #454

Type: Bug
File: Host
Desc: fixed memory problem of rules_optimize tool
Trac: #456

Type: Bug
File: Host
Desc: fixed crash with --show when using hash types which use "long" salts, e.g. -m 5600
Trac: #489

Type: Bug
File: Host
Desc: fixed output problem when using --attack-mode 1/6/7, sometimes output was truncated
Trac: #494

Type: Bug
File: Rules
Desc: Reduced generated2.rule file to 64k (65536) rules
Trac: #436

oclHashcat v1.21

Mon, 26 May 2014 14:27:29 +0000

Download here: https://hashcat.net/oclhashcat/

This release is focused on performance increase / bugfixes

As always, make sure to unpack into a new folder. Never reuse an existing oclHashcat folder (because of the cached kernels).

Added Algorithms

PHPS
Lotus Notes/Domino 5
Lotus Notes/Domino 6

Logging support

There's a new basic logfile support. It's just a start to find out if users like it or not. The log file is fomatted in a way that it is easily readable by human. The format hence is easy to parse too, each line contains a key-value pair separated by a tab character.

There will be more attributes coming in over time such as statistical information as speed and other useful information like cracked hashes. At this time, it's mostly default values, user-changed parameters, filenames of dictionary and hash.

Performance increase: New sm_50 instructions, NVidia only

With the GTX 750ti model, NVidia made an extreme move into our direction. This is the first card that supports the new sm_50 low-level instructions. For detailed information about the new sm_50 instructions, Ivan Golubev wrote an excellent blog post on here: https://www.golubev.com/blog/?p=291

To make it short, in the past AMD had a strong advantage over NVidia with their instructions BFI_INT and BIT_ALIGN. Those instructions are very useful in crypto. NVidia draw the level with the new LOP3.LUT and the SHF instruction (that was already introduced with sm_35).

Actually, the LOP3.LUT has advantage over BFI_INT. It's much more flexible and can be used in other cases as well. Additionally, NVidia added another instruction "IADD3" that can add 3 integers all at once and store the result in a fourth integer. This instruction is also very useful in crypto.

The GTX 750ti is a low-budget card, but with the next high-end card that bases on sm_50 NVidia it could be a game-changer. Also note that NVidia has much better multihash performance, not to mention the driver...

Here's how performance increased with the new low-level optimizations (yes, they will work with any other future high-end sm_50 card):

Performance increase: Workaround bad integration of 64-bit integer operations, AMD and NVidia

All the 64-bit based algorithms like SHA512, Keccak etc dropped in performance with each new driver a little bit. So it was hard to notice. GPUs instructions operate still on 32-bit only, so the 64-bit mode is emulated. But the way how it is emulated was somehow broken. I was able to pinpoint the problem where the biggest drop came from and I managed to workaround it. For NVidia it took me a little PTX hack, for AMD luckily there was no binary hack required. While this optimization is not for all algorithm as the sm_50 optimization was, therefore it works on all cards, not just the sm_50. Not much to say, let the numbers do the talk:

Changes for GCN hd7xxx / R9 series

Changes for hd5xxx / hd6xxx / Non-GCN hd7xxx series

Full Changeset

Quote:
Type: Feature
File: Host
Desc: Added support for algorithm -m 2612 = PHPS

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8600 = Lotus Notes/Domino 5

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8700 = Lotus Notes/Domino 6

Type: Workaround
File: Kernel
Desc: Fixed performance drop on descrypt, LM and oracle-old initiated by AMD drivers

Type: Workaround
File: Host
Desc: Fixed problem with restoring ADL performance state when the clock size reported by the AMD driver didn't respect the clock step size
Trac: #435

Type: Workaround
File: Host
Desc: Fixed problem with setting ADL powertune value for r9 295x2 GPUs
Trac: #438

Type: Feature
File: Host
Desc: Added support for writing logfiles
Trac: #420

Type: Feature
File: Host
Desc: Added parameter --logfile-disable which should be self-explaining
Trac: #420

Type: Change
File: Host
Desc: Dictstat is now no longer session dependent and will always be based on oclHashcat installation directory
Trac: #437

Type: Change
File: Host
Desc: Use AMD custom profile settings instead of basing the AMD powertune/clock settings on maximum supported clock values
Trac: #433

Type: Bug
File: Host
Desc: Fixed VLIW size calculated by compute capability was broken for sm_50 -> cuModuleLoad() 301

Type: Bug
File: Host
Desc: Make --runtime count relative to real attack start not program start

Type: Bug
File: Host
Desc: Fixed bug with fan speed handling, if fan speed is manually set to a high enought value (e.g. 100%) oclHashcat shouldn't change it
Trac: #439

Type: Bug
File: Host
Desc: Problem with username parsing (--username) was fixed
Trac: #441

Type: Bug
File: Host
Desc: Fixed problem where IKE-PSK sha1/md5 (-m 5300/-m 5400) were wrongly recognized as shadow file formats
Trac: #443

Type: Bug
File: Host
Desc: Fixed problem where the 'delete range' rule (xNM) did not allow to remove charaters at the very end of the word
Trac: #444

--
atom

oclHashcat v1.20

Sat, 26 Apr 2014 20:00:09 +0000

Download here: https://hashcat.net/oclhashcat/

ACHTUNG!

You will need to take some time to go through all of the release notes, as there are megatons of new features. Don't worry, it's mostly just additions, so you won't have to relearn oclHashcat's syntax all over again. However, many of the new feature require an explanation. You should know what they do, how they work, and how you can use them -- or at least, how we think you can use them.

Our goal whenever we're adding these types of features is to nurture your creativity. You are not forced to use these features in exactly the same way we suggest. Actually, we hope that some of the new features enable your neurons to fire, and inspire you with new ideas of how you can design more efficient attacks, or simply to help make the task more comfortable.

Added algorithms

Here's a quick overview about the newly-added hash types:

Juniper Netscreen/SSG (ScreenOS)
MySQL323
MD5(SHA1())
Double SHA1
SHA1(MD5())
Cisco-ASA MD5
TrueCrypt 5.0+ PBKDF2 HMAC-RipeMD160 + AES + hidden-volume
TrueCrypt 5.0+ PBKDF2 HMAC-SHA512 + AES + hidden-volume
TrueCrypt 5.0+ PBKDF2 HMAC-Whirlpool + AES + hidden-volume
TrueCrypt 5.0+ PBKDF2 HMAC-RipeMD160 + AES + hidden-volume + boot-mode
IPMI2 RAKP HMAC-SHA1
Redmine
SAP CODVN B (BCODE)
SAP CODVN F/G (PASSCODE)
Drupal7
Sybase ASE
Citrix Netscaler
1Password, cloudkeychain
DNSSEC (NSEC3)
WBB3, Woltlab Burning Board 3
RACF

You should take a close look at the SAP-B (BCODE) algorithm. AFAIK this hash is still in use in many enterprise installations. This algorithm is clearly broken! This is serious.

Also see Frank Dittrich's original writeup about the algorithm at http://www.revision-online.info/index.ph...Update.pdf
It does a decent job of explaining the weaknesses, but it was written in a time where there was no GPGPU-based cracking. Or at least, not for this algorithm.

SAP-B passwords are limited to a keyspace of 69^8. With oclHashcat v1.20, a single R9 290x can crack a hash of this type with a rate of 850 MH/s (the hd7970 is at 560 MH/s). Therefore, 8 x R9 290x can crack -every- possible SAP-B password in max. 20 hours.

The worst part about it is that the reduced keyspace is not just a matter of uppercasing the password like LM does, but it further replaces all characters outside the 0x20-0x80 ASCII range with 0xff. In other words, even if you use crazy keycodes in your password, it will be cracked in max. 20 hours. It's hopeless.

AMD Catalyst v14.x (Mantle) driver

The Mantle drivers have created some initial headaches for us. The main problem is that OpenCL binary kernels compiled for previous stable 13.x Catalyst drivers are incompatible with binary kernels compiled for Mantle drivers. So, it's not our fault that you are forced to update to Catalyst 14.x. More annoyingly, the 14.x drivers are also required if you are running Linux kernel 3.13+, so we really don't have a choice, do we?

There is an upside to upgrading to the Mantle drives, though. The OpenCL JIT compiler was updated to produce more optimized low-level instructions for the GPU, which we as developeres have no access to when using OpenCL. This means that the JIT compiler is finally starting to become as optimized as our OpenCL kernels, which translates into a 23% performance gain for NTLM.

Improved distributed cracking support

There have been a lot of different third-party approaches to distributed cracking with oclHashcat. The basic idea is simple: as in all parallel computing environments, you need to find a way to distribute the load across a set of worker nodes.

At this time, the following ideas have been developed:

Split the dictionary into N pieces, distribute the pieces to worker nodes
Split the rules into N pieces, distribute the pieces to worker nodes
Split the mask into N pieces, distribute the pieces to worker nodes
Create offsets in .restore files and distribute the restore files to worker nodes

They all work, but they are all more or less suboptimal. But that's just because oclHashcat was lacking a specific feature that developers need to make it easier, faster, and overall better.

What we added are just two parameters: -s and -l. If you are at all familar with hashcat, then you already know of these parameters, as hashcat CPU, maskprocessor and statsprocessor have had them for quite a while. They are very simple to use, and they are all you need to integrate oclHashcat into your favourite distributing system like boinc, or your own solution.

The -s and -l parameters stand for "skip" and "limit", and allow you to define a range to search within your keyspace. Parameter -s allows you to set the offset, and parameter -l allows you to set the range length. Simply divide the keyspace by the number of nodes to find the range length, and increment the offset by the range length for each node.

Here's an example: say you have a 1000-word dictionary and four identical worker nodes. So we divide the keyspace of 1000 by 4 nodes, and we get a range of 250. Your command line on each worker node will be as follows:

Code:
PC1: ./oclHashcat64.bin -s   0 -l 250 ...   // computes   0 - 249

PC2: ./oclHashcat64.bin -s 250 -l 250 ...   // computes 250 - 499

PC3: ./oclHashcat64.bin -s 500 -l 250 ...   // computes 500 - 749

PC4: ./oclHashcat64.bin -s 750 -l 250 ...   // computes 750 - 999

Now, the this example only works well when all of the nodes are identical. But sometimes you have a heterogeneous mixture of devices, and not all nodes will be the same speed. Handling failures also complicates things: what do you do if a node suddenly drops off the network? And what about if you want to add a new node while an attack is running?

To facilitate these scenarios we must take a different approach. We know the total keyspace is 1000, but this time we won't divide it by 4 because we don't know precisely how many nodes we have. Instead, we can simply use a fixed length for all nodes, and rely on the master node to keep track of the -s value. Then we can hand out work items to the nodes with a loop.

Here's an example of this approach using a fixed range length of 100.

Code:
long keyspace = 1000

long limit = 100

for (long skip = 0; skip < keyspace; skip += limit)

{

  PCxxxx: ./oclHashcat64.bin -s skip -l limit

}

This is a rudimentary and incomplete example, but it serves to demonstrate that those two parameters are all you need to distribute work, even in more complicated environments.

Now in the previous examples, calculating the keyspace was simple because we were using a dictionary attack. For dictionary attacks, the keyspace is simply the number of words in the dictionary. But it is a bit more complicated to calculate the keyspace when dealing with more advanced attack modes. Therefore, we have added another parameter called --keyspace that will calculate the keyspace for any given attack. When using a mask attack, for example, you should use --keyspace instead of trying to calculate the keyspace yourself.

Here's an example of how to use the --keyspace parameter:

Code:
atom@sf:~/oclHashcat-1.20$ ./oclHashcat64.bin some.hash -a 3 ?d?d?d?d?d?d?d?d?d --keyspace

1000000

atom@sf:~/oclHashcat-1.20$ ./oclHashcat64.bin some.hash -a 3 ?d?d?d?d?d?d?d?d --keyspace

100000

atom@sf:~/oclHashcat-1.20$ ./oclHashcat64.bin some.hash -a 3 ?d?d?d?d?d?d?d --keyspace

10000

atom@sf:~/oclHashcat-1.20$ ./oclHashcat64.bin some.hash -a 3 ?d?d?d?d?d?d --keyspace

10000

Take a close look at the last two examples. Please make life easy on yourself by using --keyspace to calculate the keyspace for all of your distributed attacks.

With all that said, we had hoped that when we started to add more distributed support it would encourage people to build more third-party distributed wrappers for oclHashcat. Already, a few beta testers have started working on such solutions. Here's an example: http://www.youtube.com/watch?v=0K4mTG5jiR8

Added outfiles directory

Soon after beta testers realized that they were now able to distribute the workload, they came up with another problem: What about the results of the cracked hashes?

Usually this doesn't matter if you are running a brute-force attack or running against an unsalted hashlist, but it's different when you have a salted hashlist. If you have a hashlist with 100 salted hashes, the time to process a keyspace is 100 timer longer than with a single salt. That should be clear, right?

oclHashcat has this optimization, as every good hash cracker should have, where if you crack all hashes bound to a specific salt, it removes that salt from the salt list and is never checked again. But in a distributed environment, there can be a node that cracked a specific salt completly by cracking all the hashes bound to it, but the other nodes do not know about that, and still process that salt unnecessarily.

We had the same problem a while back with oclHashcat-lite. It already supported -s and -l, and people were writing distributed wrappers around it. They raised the same question: what if one node cracked a hash (oclHashcat-lite was single hash), how do the other nodes know that they should stop working on it?

This eventually resulted in the following question: How to inform a running oclHashcat session with the information that a hash that it is trying to crack was cracked by a different node.

After discussing this with beta testers, we came up with a very easy solution: just put the cracked hash into a file in a directory that we call "the outfile directory." oclHashcat periodically scans the outfile directory, and reads all the files within it. For each file, and for each line in the file, it tries to match them against the internal hash table that keeps the information on which hash and which salt is cracked, and which not, and then marks it as cracked.

It's not required, but for example, to automate that process completly all you need to have is a shared directory like NFS or CIFS in which all your distributed nodes can write. Point all your nodes to write into a file in that shared directory (protip: you should use a unique file for each node.) Once a node cracks a hash, it writes it into its own outfile, and all other nodes are informed about it since they are periodically scanning the same directory.

There are some additional parameters to configure this behavior:

Patemeter "--outfile-check-dir" is the directory to periodically scan. If you do not configure it, it will be set to $session.outfiles by default
Parameter "--outfile-check-timer" can be used to configure the period in seconds to rescan the outfile directory. The default is set to 5 seconds and you can disable it by setting it to 0.

This solution also automatically stops all nodes if all hashes have been cracked, you can save some energy.

Rewrote restore system from scratch

Sometime oclHashcat is a bit pedantic. That was especially true when using --restore. It was so pedantic, I could barely use it myself. For example, restoring was only possible...

Only from the same computer. That means: same set of GPU's, same order on the PCI bus, etc. If your hardware broke, you're lost
Only from the same hashlist. In case you got cracked hashes from external sources there was no way to inform oclHashcat about it
Only from the same installation directory. In case you moved the installation directory, it was unable to restore

In theory, none of this would concern you if you were simply restoring after a power failure. But in reality, there are more complex reasons that force you to try to restore a previous session, such as hardware failure.

What we wanted was a more transparent, flexible, error-resistant and robust restore. With the new approach, you are no longer limited by the above points. There is, for instance, no more binding to the hardware or the hashlist.

But this new oclHashcat version is going much further. For example, you can now manually change the restore point. That means if you lost a .restore file for whatever reason, but you remember a position where it was, you can now set it manually. Also the size of the .restore files is now guaranteed to stay at a low filesize (somewhere < 2k).

Rewrote multihash structure

Not long ago, we had announced that it was possible to load up to 25 million hashes at once. Of course, we were talking about unsalted hashes that can be cracked with multihash techniques, not salted ones. That was not bad, but now it's even better! In 1.20, you are now able to load hashlists that contain up to 100 million hashes, and some beta testers have had success loading up to 150 million hashes. For those of you who think this is senseless, here's why we do it: Cracking huge unsalted hashlists is a great way to build new wordlists based on real passwords people use, originating from real hashdumps leaked on the Internet. Check out the compilation that KoreLogic did once, I think it was around 150 million unique MD5 hashes.

To accomplish this, we had to transition away from the previous technique where we transfered the password candiates used to crack a hash from GPU memory to host memory. Because there is no way to communicate between workgroups with OpenCL (only workitems can communicate), we were required to allocate the total amount of password buffers on the GPU, as we had the number of unique hashes multipled with the size of that password buffer. As you can imagine, that took a lot of GPU memory that could not be used for real hashes. By using a different technique that does not depend on allocating the total amount for the password buffers we can now use this memory for hashes instead.

Another thing was to speed up the process of cracking huge hashlists, which is a very memory-intensive task, we decided to increase the maximum bitmap size to 24. The bitmaps are what enable us to check for the possible nonexistence of a hash in a hashlist, before going into the costly search function. By increasing the size of the bitmap buffer, the number of unwanted collisions decreases. This increases the overall efficiency of the bitmap system, which results in an increase of overall performance.

These huge bitmaps can affect your ability to load huge hashlists, because they require a lot of GPU memory. Therefore you have a new parameter added called --bitmap-max. Usually you will never need it, but in case you want to load a huge hashlist and you get an error message from oclHashcat that it was unable to load it because the memory limit was reached, try to decrease the value of it (for example to 16) and it will save some GPU memory.

Added debugging support for rules

Most of you are already familiar with the debug parameters from hashcat CPU, and many of you wanted this feature in oclHashcat as well. Previously, it was not possible to implement this feature. However, due to the architecture changes described above, this feature is now possible.

There's a couple of new parameters to configure this new feature:

Parameter --debug-mode is used to configure whatever base-word, rule or cracked password to write
Parameter --debug-file is used to write the debugging information to a file rather than to stdout

This feature is primarily aimed for generating new rules, but it's also good if you want to find out which of your words in your dictionaries are efficient, or which rules in your rulesets crack the most hashes. But for this example, I'll only focus on the rule generator:

##
## 1. Crack some hashes with random generated rules with a small wordlist
##

Quote:
atom@ht:~/oclHashcat-1.20$ ./oclHashcat64.bin example0.hash example.dict --generate-rules 100 --debug-mode 3 --quiet
cf61d5aed48e2c5d68c5e3d2eab03241:alex999999999
alex99:Z5 Z2
a4bf29620bb32f40c3fc94ad1fc3537a:_hallo12
hallo12:^_
ba114384cc2dbf2f2e3230b803afce86:321654987Q
321654987:$Q
77719e24d4e842c8c87d91e73c7d1a8f:1123581322
1123581321:oAL *98 +8
e2a3f66b3de94593e2e0a6e5208b55af:anais20072007
anais2007:Y4
77108d6b734f4f4e06639fced921b1fe:1234qwerQ
1234qwer:$Q
66dec649460b9ebfdb3f513c2985525c:wrestlingg
wrestling:Z1
8c0d31cadefef386ed4ebb2daf1b80be:newports12
newports21:*98 p4

##
## 2. Above example is just for display of the use, usually you would do --debug-file which would contain the following information instead:
##

Quote:
atom@ht:~/oclHashcat-1.20$ cat debug.rules
alex99:Z5 Z2
hallo12:^_
321654987:$Q
1123581321:oAL *98 +8
anais2007:Y4
1234qwer:$Q
wrestling:Z1
newports21:*98 p4

##
## 3. Optimize rules with new rule-optimizer:
##

Quote:
atom@ht:~/oclHashcat-1.20$ tools/rules_optimize/rules_optimize.bin < debug.rules | sort -u
^_
*98 +8
*98 p4
$Q
Y4
Z1
Z5 Z2

What this did is removed the "oAL" function since it wasn't neccessary, thus sort -u packing rate will increase. The new rules optimizer is a standalone binary for use with debug-rules mode 3 output files, and can be found in the extra/ directory.

Over the last few days, I was running oclHashcat with -g parameter in an endless loop, always with around 10k generated rules. In total, I collected around 50k new rules, and each of them cracked at least one new hash. Then, I re-ran those 50k rules on my full dictionaries, and it had a great effect.

After a few days of letting this run in a loop, the beta testers collected a list of 600k new rules. Can you imagine that, 600k new rules. Each of them actually cracked a previously-uncracked hash. We thought this was really cool, and we wanted to share it. We ran it through the optimizer, and sorted by occurrence to have the best rules on top. We then removed all rules that did not at least crack -two- unique hashes, and the result is a list of 64k new rules sorted by occurrence. That file was name generated2.rule and added to the rules/ directory. Have fun!

Added support for $HEX[]

This addition basically goes back to the following trac ticket: https://hashcat.net/trac/ticket/148

The problem is with character encodings for various languages. To be completely honest, I really don't like this topic. There are many different encoding types, many languages, and characters. What you need to know when it comes to encoding and hashes is that most, if not all, algorithms do not care about encoding at all. Hashes algorithms just work on bytes. That means if you input a password that contains for example a german umlaut, this can result in multiple different hashes of the same unsalted algorithm. For example there are three different hashes depending if you used ISO-8859-1, utf-8 or utf-16.

We often have to deal with hashlists of unknown encoding. Therefore, the output encoding (in the shell or in the outfile) might not match with the configured encoding of our shell or our editor. The result is weird characters and user are getting confused. Worst case is if the hashlists contain mixed encodings, because the systems that generated the hashes had different encoding settings. That is something that makes our case unique, and which is why we can not simply output all plaintexts as utf-8.

Then there is more drama. There are hashes in hashlist compilations that have been put into these hashlist compilations by highly intelligent individuals. That is when they try to put in a hash into a submission mask for a hash of a complete different hash-type. For example the mask of raw MD5 but they have a salted MD5. They simply remove the salt and force in that way the acceptance from the system. Now, in combination, the problem is that some admins simply use \n, \r or even null-bytes as salt. But then, when oclHashcat is configured to automatically generate random rules it can happen that with + or - function we crack those \n salted hashes which leads to a complete different problem.

The solution is as the trac ticket suggest: if the plaintext password contains at least one character that is outside the 0x20 - 0x80 ASCII range we automatically switch the output format to $HEX[...] completely. That is a bit like utf-8 but we're not just converting the next character, we completely put the word into hex mode. Doing this, we workaround problems with:

The potfile, because the format is very simple. It works line by line and if there is a newline character in the password you password, if verified, would not match against the hash if $HEX[] was not used
The outfile, because it's not looking like weird characters when the encoding does not match to your configured one. This should help to avoid confuse unexperienced users

However, not everyone likes this feature. We added a parameter "--outfile-autohex-disable" such that oclHashcat output plains as it did with previous hashcat version.

Also note that we've added support for reading $HEX[...] encoded words from your wordlist. That is when you cracked some password that was then converted to $HEX[...] and you then merge that password with your wordlists you don't have to worry about it. oclHashcat identifies $HEX[...] encoding while reading wordlists and automatically converts them to what the words were originally.

Added tweaks for AMD OverDrive 6 and better fan speed control

This version of oclHashcat includes several changes to add better support for new AMD GPUs, i.e. OverDrive 6 enabled graphic cards. These new features range from the simple detection of OverDrive 6 GPUs, to better memory clock, core clock, powertune and fanspeed control. Since OverDrive 6 GPUs behave very different to previous AMD GPUs in what regards performance tuning (i.e. the powertune threshold and many other tuning settings need to be set to reach maximum performance), many of you may have used od6config tool by epixoip during the last months for e.g. R9 290x graphics cards. Therefore, we decided that oclHashcat should include some basic tuning support such that e.g. new users don't need to always use od6config before running oclHashcat for those cards.

Basically, this new version sets core clock, memory clock and the powertune threshold to reasonable values. The changes oclHashcat makes will always be undone after oclHashcat quits, therefore you won't need to bother about all those tuning options and the reset of it later on (because maybe you want to save eletricity). Anyway, we also added a new switch called --powertune-disable. If this switch was set, oclHashcat will skip all OverDrive 6 performance tuning steps. This way you can set this switch if you want to manually set different performance tuning options (e.g. with od6config) beforehand. We added all those powertuning change to make it more convenient for the user and to avoid that users are shocked by the low performance of OverDrive 6 cards if performance options were not manually set.

While doing all these changes, we discovered some problems with fan speed control and did try to improve this feature a lot. For instance, as mentioned here https://hashcat.net/trac/ticket/238 with previous versions it could happen that oclHashcat exits without resetting the fan speed to a reasonable value (i.e. either the speed it was before the run or the default value managed by the driver). For multi GPU setups we identified another strange behaviour with previous versions of oclHashcat and fixed it. Sometimes it could have happened that the fan speed showed N/A even if it should show the current fan speed in percentage. The problem for this unexpected behaviour was due to querying the wrong device within oclHashcat (read more about it for instance here: https://hashcat.net/trac/ticket/231 ). As you can read there, the temperature value was not accurate in some specific situations (multi gpu, windows and not all GPUs set to "active").

Adding new password candidates on-the-fly

The idea to support a way to add new password candidates (e.g. dictionary words) on-the-fly goes back to a different request that wanted a so-called loopback feature. Let me explain first what that loopback feature is.

The loopback feature makes only sense in straight-mode with rules. Whenever oclHashcat cracks a hash, the matching plain is re-queued to run through the rule-engine. So, when does this make sense?

Here's an example hashlist:

Quote:7c6a180b36896a0a8c02787eeafb0e4c
1e5c2776cf544e213c3d279c40719643

... and we have the following wordlist with just a single word:

Quote:password

... and a simple rule that append a 1 to each word from the wordlist:

Quote:$1

When I run this, it will crack one of the above hashes:

Quote:7c6a180b36896a0a8c02787eeafb0e4c:password1

Now, with the loopback feature enabled, it will take "password1" as a new candidate and the rule $1 is applied. It will now crack:

Quote:1e5c2776cf544e213c3d279c40719643:password11

This goes on and on, until there is no new hash cracked and therefore new password re-added to the queue.

Where is this useful in real life? For example when cracking millions of hashes at once to build you dictionaries. If you run it with many rules chances are good to automatically detect a pattern in that hashlist.

Now we can go back to the password candidates on-the-fly. When we thought about how to add that request we came up with the idea of the induction directory. This directory can be defined with the new parameter "--induction-dir" or you skip specifying it and oclHashcat will define it as $session.induct. oclHashcat will create that directory for you automatically (and remove it afterwards). While oclHashcat is running you can put files into that new directory which will be scanned by oclHashcat as soon as the current dictionary finishes.

Rewrote weak-hash check

This feature goes back to the following trac ticket: https://hashcat.net/trac/ticket/165

Note that our implementation is not exactly as it was requested in the ticket.

I'll explain: The goal of this feature is to notice if there is a hash whose plaintext is empty, that means a 0-length password. Typically when you just hit enter. We call it a weak-hash check even if it should have been called weak-password check but there are simply too many weak-passwords.

Previous version did support this, but only for unsalted hashes. That was easy to implement because on unsalted hashes the 0-length password always results in the same hash. By simply checking that hash, it was possible to find out if it's used. Thing is getting more complicated when a salt is involved. That means that we actually have to run the kernel and create a 0-length password result but with exactly that salt. But that wasn't too easy because oclHashcat has different attack-modes and depending on which attack-mode you choose a different kernel is loaded. Therefore the attack parameters change and we have to create different 0-length password attacks for each attack-mode a user can choose. But that's not all. There are also many differences if some special parameters are set for slow hashes and for fast hashes. That were those problems to solve just to get it working, but that's done, no more headache with this.

The next problem, however, is if your hashlist contains millions of salts. As already explained above, we have to run a kernel for each salt. If you want to check for empty passwords for that many salts you will have a very long initialization/startup time by running oclHashcat. To work around this problem we added a parameter called "--weak-hash-threshold". With it you can set a maximum number of salts for which weak hashes should be checked on start. The default is set to 100, that means if you use a hashlist with 101 unique salts it will not try to do a weak-hash check at all. Note we are talking about unique salts not unique hashes. Cracking unsalted hashes results in 1 unique salt (an empty one). That means if you set it to 0 you are disabling it completely, also for the unsalted hashes.

Reload previously-cracked hashes from potfile

With this feature added, oclHashcat will read the potfile every time oclHashcat starts and compares the content of the .pot file (the cracked hashes) with the hashes from the hashlist it is trying to crack. This is something that is present in JtR, and JtR users will alredy know how this works, but we've added it for a different reason.

When we rewrote the restore feature, we had that problem that, in case of a restore, oclHashcat did not know which hash were already cracked in the previous run. Unless you use --remove, which automatically removes all cracked hashes from your hashlist in real-time, it would start cracking the same hashes again, depending on your attack-type.

There's just one solution: you need to keep track of the hashes that have been cracked already, and compare it on every start with the hashlist. This is typically a very fast process, but if you have a lot of entries in your potfile, it can take some time. However, it is save to remove the potfile if you don't need it any longer. The potfile name is $session.potfile. If you dont want to remove the potfile you can also skip the loading delay by disabling the use of this new feature with the "--potfile-disable" flag completetly. But note, this also disables the writing of it. If you crack a hash it will create confusion if you want to restore a session. Make sure you know what you do.

The way this feature compares and finds hashes is basically the same as when reading files from the outfile directories.

Full Changeset

Quote:
Type: Driver
File: Kernel
Desc: Added support for AMD Catalyst v14.4 (mantle) driver

Type: Driver
File: Kernel
Desc: Added support for AMD new GPUs: "Spectre", "Spooky", "Kalindi", "Hainan", "Iceland", "Tonga" and "Mullins"

Type: Driver
File: Kernel
Desc: Added support for NV ForceWare 331.67 driver

Type: Driver
File: Kernel
Desc: Added support for NV new GPUs: "sm_50" (Maxwell)

Type: Reimplementation
File: Kernel
Desc: Rewrote multihash structure, ex: 290x can now load up to 100,000,000+ MD5/NTLM hashes at once

Type: Reimplementation
File: Kernel and Host
Desc: Rewrote rule engines (CPU and GPU) and made them more robust by synchronizing error handling

Type: Reimplementation
File: Host
Desc: Rewrote restore system from scratch; no longer requires same system with same GPUs

Type: Reimplementation
File: Host
Desc: Restructured .restore file; no longer create huge .restore files, stay < 2k of size

Type: Reimplementation
File: Host
Desc: Rewrote weak-hash check; support all algorithm types including salted ones
Trac: #165

Type: Reimplementation
File: Host
Desc: Rewrote workload dispatching when progress is near to keyspace end; act more conservative

Type: Reimplementation
File: Host
Desc: Rewrote mechanism to control the fan with AMD GPUs

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 22 = Juniper Netscreen/SSG (ScreenOS)
Trac: #235

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 200 = MySQL323
Trac: #377

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 1421 = hMailServer
Trac: #401

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 2410 = Cisco-ASA MD5
Trac: #365

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 4400 = md5(sha1($pass))
Trac: #198

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 4500 = Double SHA1
Trac: #390

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 4700 = sha1(md5($pass))
Trac: #198

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 4800 = MD5(Chap), iSCSI CHAP authentication
Trac: #214

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 6251 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + AES + hidden-volume
Trac: #378

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 6261 = TrueCrypt 5.0+ PBKDF2-HMAC-SHA512 + AES + hidden-volume
Trac: #378

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 6271 = TrueCrypt 5.0+ PBKDF2-HMAC-Whirlpool + AES + hidden-volume
Trac: #378

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 6281 = TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + AES + hidden-volume + boot-mode
Trac: #378

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 7300 = IPMI2 RAKP HMAC-SHA1
Trac: #233

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 7600 = Redmine Project Management Web App
Trac: #391

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 7700 = SAP CODVN B (BCODE)
Trac: #177

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 7800 = SAP CODVN F/G (PASSCODE)
Trac: #177

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 7900 = Drupal7
Trac: #326

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8000 = Sybase ASE
Trac: #193

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8100 = Citrix Netscaler
Trac: #369

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8200 = 1Password, cloudkeychain
Trac: #126

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8300 = DNSSEC (NSEC3)
Trac: #387

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8400 = WBB3, Woltlab Burning Board 3
Trac: #181

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8500 = RACF
Trac: #192

Type: Feature
File: Kernel
Desc: Added support for $2y$ and $2a$ bcrypt signatures
Trac: #251

Type: Feature
File: Kernel
Desc: Added support for higher cost factors for -m 400 = phpass
Trac: #280

Type: Feature
File: Kernels
Desc: Increased support for username length up to 20 for -m 1100 = Domain Cached Credentials, mscash
Trac: #379

Type: Feature
File: Kernels
Desc: Increased support for username length up to 20 for -m 2100 = Domain Cached Credentials2, mscash2
Trac: #379

Type: Feature
File: Kernels
Desc: Added support for mixed cracking WPA and WPA2 at once, no more need for split
Trac: #388

Type: Feature
File: Host
Desc: Added support for Tesla Deployment Kit v5.319.85

Type: Feature
File: Host
Desc: Added parameter --workload-profile to give the user a convenient way to set the reduced, default or tuned performance tuning options

Type: Feature
File: Host
Desc: Added parameter -s for use in distributed computing, mark skip of range of keyspace

Type: Feature
File: Host
Desc: Added parameter -l for use in distributed computing, mark length of range of keyspace

Type: Feature
File: Host
Desc: Added parameter --keyspace for use in distributed computing, calculate keyspace

Type: Feature
File: Host
Desc: Load already cracked hashes from potfile on startup to avoid double cracking

Type: Feature
File: Host
Desc: Added inline induction directory that can be used for on-the-fly adding of new password candidates

Type: Feature
File: Host
Desc: Added switch --loopback to automatically write cracked plains into a file in the induction directory

Type: Feature
File: Host
Desc: Added debugging support for rules as in hashcat CPU; used for rule- and dictionary efficiency analysis

Type: Feature
File: Host
Desc: Added parameter --debug-mode and --debug-file to write found plains and/or rules as in hashcat CPU

Type: Feature
File: Host
Desc: Added --debug-mode 4 == original_plain:rule:modified_plain
Trac: #317

Type: Feature
File: Host
Desc: Added tweaks for AMD OverDrive 6 (powercontrol, core- and mem-clock profiles)

Type: Feature
File: Host
Desc: Added switch --powertune-disable to allow users to disable automatic power tuning for AMD OverDrive 6

Type: Feature
File: Host
Desc: Added --induction-dir to allow the users to specify the folder which will be used instead of the default induct folder

Type: Feature
File: Host
Desc: Added --outfile-check-dir to allow the users to specify the folder which should be monitored for cracked hashes

Type: Feature
File: Host
Desc: Added --outfile-check-timer to allow the users to control the outfile/potfile reading frequency (0 = disabled)

Type: Feature
File: Host
Desc: Added periodic outfile reading such that user can remove hashes while cracking by appending the hash[alt]:plain to the file

Type: Feature
File: Host
Desc: Added support for automatic detection for hashfile-formats like pwdump, passwd, shadow, etc.
Trac: #393

Type: Feature
File: Host
Desc: Undo fan speed changes by oclHashcat after stopping/aborting
Trac: #238

Type: Feature
File: Host
Desc: Added support loading $HEX[...] format from dictionaries

Type: Feature
File: Host
Desc: Added switch --outfile-autohex-disable to disable $HEX[...] format

Type: Feature
File: Host
Desc: Added switch --hex-wordlist to enable parsing words in wordlists given in hex

Type: Feature
File: Host
Desc: Increased maximum bitmap size to 24 bits to speed up cracking of huge hashlists at once

Type: Feature
File: Host
Desc: Added parameter --bitmap-max to help loading huge hashlists and with small gpu ram

Type: Feature
File: Host
Desc: Added parameter --weak-hash-threshold to set a maximum number of salts for which weak hashes should be checked

Type: Feature
File: Host
Desc: Added parameter --remove-timer to set the frequency the hash-file should be updated when using --remove

Type: Feature
File: Host
Desc: Added bit for parameter --outfile-format to print the position of a candidate that cracked a hash

Type: Feature
File: Host
Desc: Added parameter --status-automat to let oclHashcat display the status view in a machine readable format
Trac: #406

Type: Feature
File: Host
Desc: Added column "Skipped" to status display to showing skipped candidates because of cracked salt(s)

Type: Feature
File: Host
Desc: Improved handling of signals and terminate events; SIGTERM support and windows cmd close handling
Trac: #143

Type: Feature
File: Host
Desc: Added ability to use restore files from previous versions in case the structure did not change

Type: Feature
File: Host
Desc: Set default retain and abort temperatures for AMD OverDrive6 GPUs according to the values reported by ADL
Trac: #225

Type: Feature
File: Host
Desc: Added parameter -v to displays the version string (as -V does)
Trac: #252

Type: Feature
File: Host
Desc: Added support to load and save invalid salt characters used in descrypt
Trac: #269, #405

Type: Feature
File: Host
Desc: Added support for variable iteration number for -m 2100 = mscash2
Trac: #380

Type: Feature
File: Host
Desc: outfile-check and potfile remove (at startup) can now also be used together with hash mode 2500 = WPA/WPA2 and 6800 = Lastpass
Trac: #400

Type: Feature
File: Host
Desc: Added rules_optimizer standalone binary for use with debug-rules mode 3 output files

Type: Feature
File: Host
Desc: While parsing hashes on start inform user about the progress

Type: Feature
File: Rules
Desc: Added InsidePro-HashManager.rule

Type: Feature
File: Rules
Desc: Added generated2.rule, each one cracked a real hash, sorted by occourance. use head -XXXX to make a top XXXX
Cred: EvilMog

Type: Change
File: Rules
Desc: Renamed passwordspro.rule to InsidePro-PasswordsPro.rule

Type: Change
File: Host
Desc: Modified output plains to $HEX[...] format in case cracked password contains chars outside 0x20 - 0x80 ASCII range
Trac: #148

Type: Change
File: Host
Desc: Modified switch --potfile-disable to disable loading already cracked hashes from potfile on startup

Type: Change
File: Host
Desc: Save potfile and dicstat in the current working directory instead of installation directory
Trac: #281

Type: Change
File: Host
Desc: Change input hash format for -m 2100 = mscash2
Trac: #380

Type: Change
File: Host
Desc: Update tab completion for bash (in extra folder) to match up with new parameters

Type: Change
File: Host
Desc: Renamed switch --disable-potfile to --potfile-disable to match up parameter logic

Type: Change
File: Host
Desc: Renamed switch --disable-restore to --restore-disable to match up parameter logic

Type: Change
File: Docs
Desc: Help and docs update to underline that OSX 10.9 uses same format as 10.8
Trac: #236

Type: Change
File: Docs
Desc: Help and docs update to underline that MSSQL(2014) uses same format as MSSQL(2012)

Type: Change
File: Docs
Desc: Removed examples.txt; see wiki for more information
Trac: #236

Type: Change
File: Host
Desc: Renamed hash type Joomla into 'Joomla < 2.5.18', -m 400 has now also the note about MD5(Joomla)
Trac: #402

Type: Bug
File: Kernel
Desc: Raw whirlpool -m 6100 hashes could not be cracked in -a 1 combinator mode

Type: Bug
File: Host
Desc: If increment and masks were used in combination, status display needs reset to INIT after each iteration

Type: Bug
File: Host
Desc: In attack-mode 1 and 7, if at least one word in right wordlist is exactly of length 31, memory corruption occoured over time

Type: Bug
File: Host
Desc: Status timer should be enabled by default when in stdin mode
Trac: #218

Type: Bug
File: Host
Desc: Improved reading of fan speed and temperature; It sometimes failed when using twin GPUs on windows
Trac: #231

Type: Bug
File: Host
Desc: File handling ('Permission denied' error) fixed when using --remove with -m 2500
Trac: #395

Type: Distribution
File: Packages
Desc: Created two packages for download: oclHashcat-* for AMD, cudaHashcat-* for CUDA

One last thing: With this update you'll be able to load pwdump, passwd and shadow unmodified. If you want other native formats added, please update this ticket: https://hashcat.net/trac/ticket/393

--
atom

oclHashcat v1.01

Tue, 31 Dec 2013 23:42:49 +0000

Download here: http://hashcat.net/oclhashcat/

Full changelog

Quote:
type: driver
file: kernels
desc: added support for AMD Catalyst v13.12

type: feature
file: host programs
desc: added --generate-rules-seed, sets seed used for randomization so rulesets can be reproduced

type: feature
file: host programs
desc: updated/added some hcchr charset files in /charsets, some new files: Bulgarian, Polish, Hungarian
cred: Rub3nCT

type: bug
file: host programs
desc: when using -m 2500 w/ multi hccap files there was no error shown if the user mixed WPA and WPA2 networks, this is currently not allowed
trac: #222

oclHashcat v1.00

Fri, 06 Dec 2013 21:41:20 +0000

Download here: http://hashcat.net/oclhashcat/

oclHashcat v1.00 is a fusion of oclHashcat-plus v0.15 and oclHashcat-lite v0.15

The reason for fusion was:

Simplify the project! Users were confused which tool among -lite and -plus they should choose.
Fusioned oclHashcat will automatically decide which kernel type to choose based on the attack-mode and the hash-type you selected
Save maintaining two programs with nearly the same codebase
Save disk-space and packages

This release is alot about performance and bugs

While -plus v0.15 focused on supporting password candidates with length 15+, which in some cases reduced cracking speed, we can say that with oclHashcat v1.00 most of the speed loss that inevitabely was introduced with -plus v0.15 got compensated for many hash types by heavily optimizing the new kernels (e.g. merging -plus kernels with -lite and continuing optimizing the resulting kernel). You will see some nice increase of cracking speed for some hash-types (e.g. raw MD5 on NVidia from ~1600MH/s -> 1800MH/s), see benchmarking section.

We've also written an fully automated testing system, cross-platform. We found some bugs which were all fixed. If you want to try it on your system just come to IRC and we'll instruct you how to run it.

Workaround driver problems

Whenever AMD or NVidia releases new drivers we have to check if our code still works. Most of the time it just works, but sometimes they add bugs to their driver that influences (or heavily influences) oclHashcat.

One example was the Catalyst 13.8beta driver, which is known to have some bugs that influence oclHashcat. We had to mark it as "broken" and were printing out a warning message whenever a user wanted to run -lite or -plus using this driver.

That was a very restrictive way of handling that type of problem and made package maintainers mad. This behavior forced the distribution to stick to a specific driver version. So we decided to find out where the bugs in the drivers are and then try to workaround them.

That done, we worked around all (known) bugs so you will be able to use all drivers from Catalyst 13.4 and upwards.

Built-in benchmarking system

While this feature was in -lite for some time, it's new for -plus users. This "tool" will show you which maximum performance you can get out of your system in an ideal cracking case. Such a case is usually trying to crack a single hash using the brute-force attack mode, because we can make use of a lot of different optimization techniques.

It has been fine-tuned to use near-to-perfect tuned workloads (-n and -u parameters) and it is using a huge keyspace. Whenever you run an attack there are many factors that can influence cracking speed. By using the benchmark system you can get an idea what your maximum possible cracking speed could be and optimize your attack.

Most of the basic commandline parameters can be used in addition, for example you can use -d to select which GPU(s) or card(s) to run in benchmark mode. Or, if you want to benchmark just a single hash type you can use the -m parameter.

There are two different benchmark-modes. The default sets the configuration to run in benchmark-mode 1, which is the more aggressive one. It's what most people will use and thats it. If you switch to benchmark-mode 0 you can manually tune -n and -u value to even more aggressive values but make sure you have good GPU cooling.

It's also a very simple way to benchmark your system and compare it with others. To have some fun after downloading oclHashcat v1.00 just run it with e.g. "./oclHashcat64.bin -b", that's it.

Multi-hccap support

Starting with this release, oclHashcat supports .hccap files for WPA cracking that include several networks (both with different or same ESSID). The file format is basically using the same struct as before, but one .hccap file can now consist of several such structures.

This implies that you could simply merge two or more .hccap files together into a new .hccap file that contains all of the merged information. A simple "cat 1st.hccap 2nd.hccap > all.hccap" should suffice to get you started with this new feature (on windows use an equivalent command).

Support for new algorithms

HMAC-* (key = $pass)
HMAC-* (key = $salt)
sha1(LinkedIn)
Kerberos 5 AS-REQ Pre-Auth etype 23

* = MD5, SHA1, SHA256, SHA512

Full changelog

Quote:
* initial version 1.00

first public release, oclHashcat is a fusion of oclHashcat-plus v0.15 and oclHashcat-lite v0.15

type: driver
file: kernels
desc: added support for AMD Catalyst v13.8b*

type: driver
file: kernels
desc: added support for AMD Catalyst v13.9

type: driver
file: kernels
desc: added support for AMD Catalyst v13.11b*

type: driver
file: kernels
desc: added support for AMD R9 series

type: driver
file: kernels
desc: added support for AMD APP SDK v2.9

type: feature
file: kernels
desc: added -m 50 = HMAC-MD5 (key = $pass)

type: feature
file: kernels
desc: added -m 60 = HMAC-MD5 (key = $salt)

type: feature
file: kernels
desc: added -m 150 = HMAC-SHA1 (key = $pass)

type: feature
file: kernels
desc: added -m 160 = HMAC-SHA1 (key = $salt)

type: feature
file: kernels
desc: added -m 190 = sha1(LinkedIn)
trac: #190

type: feature
file: kernels
desc: added -m 1450 = HMAC-SHA256 (key = $pass)
trac: #97

type: feature
file: kernels
desc: added -m 1460 = HMAC-SHA256 (key = $salt)
trac: #97

type: feature
file: kernels
desc: added -m 1750 = HMAC-SHA512 (key = $pass)

type: feature
file: kernels
desc: added -m 1760 = HMAC-SHA512 (key = $salt)

type: feature
file: kernels
desc: added -m 7500 = Kerberos 5 AS-REQ Pre-Auth etype 23

type: feature
file: host programs
desc: added tab completion feature for bash in extra folder

type: feature
file: host programs
desc: added support for Tesla Deployment Kit v5.319.43

type: feature
file: host programs
desc: added support for NVAPI R319

type: feature
file: host programs
desc: added --benchmark, run several hash modes in benchmark mode for speed tests

type: feature
file: host programs
desc: added --disable-restore option, don't write/update nor touch restore file

type: feature
file: host programs
desc: added --cleanup-rules, remove rules that couldn't be used or have duplicates. A .bak backup file will be created
trac: #139

type: feature
file: host programs
desc: added support for hccap files containing several networks
trac: #167

type: feature
file: host programs
desc: show the status by hitting the s key or the Enter key, show the status when dict or mask changed
trac: #189

type: feature
file: host programs
desc: show line progress for maskfiles (.hcmask)
trac: #206

type: rules
file: T0XlC.rule
desc: cleaned, original T0XlC.rule
cred: T0XlC

type: rules
file: T0XlCv1.rule
desc: added ruleset with 12000 random rules
cred: T0XlC

type: rules
file: T0XlC_insert_00-99_1950-2050_toprules_0_F.rule
desc: added ruleset with insert rules from position 0 to position F (00-99,1950-2050)
cred: T0XlC

type: rules
file: T0XlC_insert_space_and_special_0_F.rule
desc: added ruleset with insert rules from position 0 to position F (special characters)
cred: T0XlC

type: rules
file: T0XlC_insert_top_100_passwords_1_G.rule
desc: added ruleset with insert rules from position 0 to position F (top 100 passwords)
cred: T0XlC

type: bug
file: host programs
desc: problem while performing the --remove operation in windows fixed - timing problem (Permission denied error)

type: bug
file: host programs
desc: Fixed mask length display in status screen when using hash types that internally use unicode

type: bug
file: host programs
desc: Hash files that did not end with a newline character were not parsed correctly

type: bug
file: host programs
desc: Fixed crash when hitting CTRL-C, when receiving abort signals

type: bug
file: host programs
desc: Fixed freeze, flush problem w/ progress at ~100%
trac: #82

type: bug
file: host programs
desc: Fixed russian charset files (hcchr), removed unnecessary chars
trac: #194

type: bug
file: host programs
desc: Fixes a crash when using --username together with --remove
trac: #197

type: change
file: host programs
desc: new default status-timer value is 10 seconds instead of 1 minute