hashcat Forum

Pages: 1 2 3

I was wondering if I'm on the right track using something like this:

hashcat64.exe -a 3 example0.hash NotTheRealPassI'mNotThatClueless?a?a?a -o cracked.txt
pause

I also found the encryption file for my wallet where I saw the "cipher" was "cipher":"aes-128-ctr" as well as some parameter and salt (which I read a few time, yet have no idea what it is about).

Anyone care to explain how to set the right hash type and use the salt? I couldn't see any aes 128 in the list in the wiki.

use https://github.com/magnumripper/JohnTheR...um2john.py to extract the necessary info from your wallet

you're on the right track. To set the hash type consult --help (and see my previous post)

(08-08-2017, 06:42 PM)undeath Wrote: [ -> ]depends, if your wallet is mode 15600 [$ethereum$p] use your GPU (mining rig) if your wallet is mode 15700 [$ethereum$s] use your CPU (gaming machine) still use your mining rig

(well, actually it might still be worth trying mode 15700 with your mining rig GPUs, my 2600k does 13 H/s while my single 1060 does 21 H/s)

Ah, that info is part of what I needed. Couldn't find the hash type but using johntheripper file you linked me to, I found it was [$ethereum$s] so it must be the 15700, named ethereum wallet, scrypt in the list. Again, thanks!

Now, I need to figure what to do with those 2 lines of random character it writes.
Should I copy the " $ethereum$s*262234*8*1*d643 etc etc etc" in some new files and use this as the hash file?

My new cmd file looks like this, with the example0.hash which looks to countain the wrong info (copied/pasted the JohnTheRipper output to this file).

hashcat64.exe -a 3 -m 15700 -D 2 example0.hash NotTheRealPassI'mNotThatClueless?a?a?a -o cracked.txt
pause

Yeah,but wait for confirmation from that undead guy.

BTW,why couldn't you create an empty .txt file and copy your hash over there?it was better.

Changing from -D 2 to -D 1 (cpu instead of GPU) I got it working, but slowly (4H/s on the 4790k ?). About 2d 12hr for the 857k possibilities.

I am having some error when trying to use the gpu. Read at some place older version doesn't get it so I'll try it later tonight.

4 H/s is really slow. Something seems off. As written before, my old 2600k manages to get 13 H/s. But why not using your GPU? It's probably still at least as fast as your CPU. Note that it may take ~2 minutes for hashcat to accurately reflect the hash rate for a slow mode such as 15700.

Because I'm getting error with allocated memory as soon as I try the -D 2 instead of -D 1. Seems like it doesn't love my gpu, on the 3 machine I tried it.
I tried the -n 1 option as suggested, but it told it was out of date. Tried to force it but it didn't work, as when I do, it gives back the error about allocated memory and the need to try -n 1. Might be writting the command wrong.

hashcat64.exe -a 3 -m 15700 -w 1 --scrypt-tmto 1 --force -n 1 -D 2 hash.hash SomePassword?a?a?a -o cracked.txt

Code:
hashcat (v3.6.0) starting...

* Device #1: Intel's OpenCL runtime (GPU only) is currently broken.

            We are waiting for updated OpenCL drivers from Intel.

            You can use --force to override, but do not report related errors.

* Device #3: WARNING! Kernel exec timeout is not disabled.

            This may cause "CL_OUT_OF_RESOURCES" or related errors.

            To disable the timeout, see: https://hashcat.net/q/timeoutpatch

OpenCL Platform #1: Intel(R) Corporation

========================================

* Device #1: Intel(R) HD Graphics 4600, skipped.

* Device #2: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz, skipped.

OpenCL Platform #2: NVIDIA Corporation

======================================

* Device #3: GeForce GTX 980 Ti, 1536/6144 MB allocatable, 22MCU

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 1.

Cannot allocate enough device memory. Perhaps retry with -n 1.

Started: Wed Aug 09 05:37:18 2017

Stopped: Wed Aug 09 05:37:19 2017

C:\Users\Dumb\Desktop\hashcat-3.6.0>pause

I just looked at the wiki for the various option that were used. -w 1 was causing slowdown on the 4790k. moving it to -w 2 and I'm getting 12-14 h/s.
The gpu still won't work on my 3 pc and mining rig.

Code:
C:\Users\Miner 1\Desktop\hashcat-3.6.0>hashcat64.exe -a 3 -m 15700 -w 2 --scrypt-tmto 1 -n 1 -D 2 --force hash.hash Otherpass?a?a?a -o cracked.txt

hashcat (v3.6.0) starting...

OpenCL Platform #1: Intel(R) Corporation

========================================

* Device #1: Intel(R) Celeron(R) CPU G3930 @ 2.90GHz, skipped.

OpenCL Platform #2: NVIDIA Corporation

======================================

* Device #2: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU

* Device #3: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU

* Device #4: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU

* Device #5: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU

* Device #6: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU

* Device #7: GeForce GTX 1070, 2048/8192 MB allocatable, 15MCU

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 1.

Cannot allocate enough device memory. Perhaps retry with -n 1.

Started: Wed Aug 09 02:55:30 2017

Stopped: Wed Aug 09 02:55:33 2017

C:\Users\Miner 1\Desktop\hashcat-3.6.0>pause

Press any key to continue . . .

In the similar post you helped with : https://hashcat.net/forum/thread-6648-page-2.html

The guy says it worked with 3.6 clean build (which I use) and moving openCL file. What are those needed files?

Did you try --scrypt-tmto=0? At least the example hash works for me with every tmto setting (though 0 is the fastest option on cpu and gpu in my scenario).

--force is only if you use an unsupported driver.

The moving of files mentioned in the other thread was a Mac-specific issue.

I only tried it with -scrypt-tmto 1
Will see when I get back from work if going to 0 change something.

Pages: 1 2 3

DumberThanDumb

undeath

DumberThanDumb

slayerdiangelo

slayerdiangelo

DumberThanDumb

undeath

DumberThanDumb

undeath

DumberThanDumb