hashcat Forum

Full Version: OSX 10.12.6 Sierra - Token length exception
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Gents.

Did my due diligence and scoured the interwebs for info in regard to OSX and the Token length exception that hashcat is throwing me - for the extracted hash's.

Running OSX v10.12.6 Sierra

1. I created a user - 'temp' with a password 'password'.
2. Created a short dictionary file with simply 'password' within it.
3. Extracted the hash using a variety of methods, all yield the same string, of the same length.
4. Compared it against the sample hash provided on the site, it's a clear 128 hex characters longer than the sample.

I've read to truncate the string - tried that - ran hashcat, no result, despite the known password matching the word in the dictionary.

Guess my question is - did something change in OSX 10.12 - making the string longer somehow. And if that's the case, is there a workaround, or will there be support for 10.12 in the future?

Thanks guys.
rp

had 3 hash's in the hash.txt file - two i extracted, and one from the sample page...

output:

rp-iMac:hashcat rp$ ./hashcat -a 0 -m 7100 hash.txt dict.simple
hashcat (v5.1.0-1511-g2a043544) starting...

OpenCL API (OpenCL 1.2 (Apr 18 2019 20:04:11)) - Platform #1 [Apple]
====================================================================
* Device #1: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, skipped
* Device #2: ATI Radeon HD 6970M, 960/1024 MB (256 MB allocatable), 12MCU

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256

Hashfile 'hash.txt' on line 1 ($ml$46...xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx): Token length exception
Hashfile 'hash.txt' on line 2 ($ml$27...xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx): Token length exception
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Slow-Hash-SIMD-LOOP
* Uses-64-Bit

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

Host memory required for this attack: 204 MB

* Device #2: ATTENTION! OpenCL kernel self-test failed.

Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver

Aborting session due to kernel self-test failure.

You can use --self-test-disable to override this, but do not report related errors.

Started: Mon Dec 16 11:28:03 2019
Stopped: Mon Dec 16 11:28:04 2019
rp-iMac:hashcat rp$
https://github.com/hashcat/hashcat/issue...-425702306

you can just truncate it (to the same length the example hash has https://hashcat.net/wiki/example_hashes)


The more serious problem is your driver issue "kernel self-test failed". this is a serious problem that most of the time only your driver manufacturer can fix with an update (i.e. with a working and therefore non-buggy OpenCL driver)

You can probably use -D 1 for testing with your CPU