hashcat Forum

Full Version: Works great, except for ethereum
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Couldn't get -m 15700 (ethereum scrypt) working for me.

I have a hash of "Hi"

{"address":"6fea59d03567729c41545e9d6b22e970d03e0c6a","crypto":{"cipher":"aes-128-ctr","ciphertext":"04a4813a25457cc354d29a669c8d47893b642d3b999f2c89876d3756c23b0f6e","cipherparams":{"iv":"42781602a9a10147f572e935f8cecefc"},"kdf":"scrypt","kdfparams":{"dklen":32,"n":262144,"p":1,"r":8,"salt":"03b394784c4598d1b803661ddf6e7204cf1d85f99793cdbe8920964aaa5f3af5"},"mac":"9c1442d8f46951b6048fd3e8ca51ae82ae0b7f23d859f8a96c25e646d0ed56dd"},"id":"eb03b2a9-b5a0-4fd6-b855-e70469f2f9e4","version":3}

This is with Debian Sid's binary...
Code:
❯ hashcat --version

pull/1273/head

❯ hashcat -d 1 -m 15700 -a 3 -1 '?u?a' -i --increment-min 1 --status ~/hi.json '?1?1'
hashcat (pull/1273/head) starting...

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080 Ti, 2793/11172 MB allocatable, 28MCU
* Device #2: GeForce GTX 1080 Ti, skipped.
* Device #3: GeForce GTX 1080, skipped.

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force

Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 4.
SCRYPT tmto optimizer value set to: 5, mem: 7516192768

* Device #1: build_opts '-I /usr/share/hashcat/OpenCL -D VENDOR_ID=32 -D CUDA_ARCH=601 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll -cl-std=CL1.2'
s

[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework

Approaching final keyspace - workload adjusted.

[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => s

Session..........: hashcat
Status...........: Running
Hash.Type........: Ethereum Wallet, SCRYPT
Hash.Target......: $ethereum$s*262144*8*1*8247c9a67ea11366a96081d040e1...eaeb8d
Time.Started.....: Sat Jul 29 22:41:44 2017 (1 sec)
Time.Estimated...: Sat Jul 29 22:41:45 2017 (0 secs)
Guess.Mask.......: ?1 [1]
Guess.Charset....: -1 ?u?a?a?a, -2 Undefined, -3 Undefined, -4 Undefined
Guess.Queue......: 1/8 (12.50%)
Speed.Dev.#1.....:        0 H/s (0.00ms)
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0/95 (0.00%)
Rejected.........: 0/0 (0.00%)
Restore.Point....: 0/1 (0.00%)
Candidates.#1....: s -> s
HWMon.Dev.#1.....: Temp: 48c Fan: 33% Util:100% Core:1987MHz Mem:5005MHz Bus:1

It seems like it never starts.

I also tried with latest from source.

Code:
❯ ./hashcat -d 1 -m 15700 -a 3 -1 '?u?a' -i --increment-min 1 --status ~/hi.json '?1?1'
hashcat (v3.6.0-271-g942b7068) starting...

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080 Ti, 2793/11172 MB allocatable, 28MCU
* Device #2: GeForce GTX 1080 Ti, skipped.
* Device #3: GeForce GTX 1080, skipped.

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force

Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

Increasing single-block device memory allocatable for --scrypt-tmto 0.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
Increasing single-block device memory allocatable for --scrypt-tmto 4.


[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => s


[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => s

This time when I press s, it doesn't say anything.

md5 works perfectly
hashcat -d 1 -m 0 -a 3 -1 '?u?a' --increment --increment-min 1 ~/md5 '?1?1'

Here is my opencl-info
Code:
❯ hashcat -D 1 --opencl-info
hashcat (pull/1273/head) starting...

OpenCL Info:

Platform ID #1
  Vendor  : NVIDIA Corporation
  Name    : NVIDIA CUDA
  Version : OpenCL 1.2 CUDA 8.0.0

  Device ID #1
    Type           : GPU
    Vendor ID      : 32
    Vendor         : NVIDIA Corporation
    Name           : GeForce GTX 1080 Ti
    Version        : OpenCL 1.2 CUDA
    Processor(s)   : 28
    Clock          : 1683
    Memory         : 2793/11172 MB allocatable
    OpenCL Version : OpenCL C 1.2
    Driver Version : 375.82

Let me know if there is anything I can try to help debug this.

Thanks!
SCRYPT is an anti-gpu algorithm, you can expect strange behavior especially with such high SCRYPT settings. Let it run for a few minutes or hours and do not interrupt. Or simply use a CPU device for "normal" behavior:

Quote:Session..........: hashcat
Status...........: Cracked
Hash.Type........: Ethereum Wallet, SCRYPT
Hash.Target......: $ethereum$s*262144*8*1*03b394784c4598d1b803661ddf6e...ed56dd
Time.Started.....: Sun Jul 30 12:58:22 2017 (26 secs)
Time.Estimated...: Sun Jul 30 12:58:48 2017 (0 secs)
Guess.Mask.......: ?a?a [2]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 15 H/s (522.85ms)
Recovered........: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.........: 400/9025 (4.43%)
Rejected.........: 0/400 (0.00%)
Restore.Point....: 0/95 (0.00%)
Candidates.#1....: Ha -> Hh
HWMon.Dev.#1.....: N/A