mirror of
https://github.com/hashcat/hashcat.git
synced 2024-11-21 23:58:07 +00:00
Update tunings/Module_29800.hctune to reflect right hash-mode
This commit is contained in:
parent
1e5e7735dc
commit
1bbf9a68a0
@ -2,13 +2,13 @@
|
||||
# Find the right -n value for your GPU:
|
||||
# =====================================
|
||||
#
|
||||
# 1. For example, to find the value for 27700, first create a valid hash for 27700 as follows:
|
||||
# 1. For example, to find the value for 29800, first create a valid hash for 29800 as follows:
|
||||
#
|
||||
# $ ./hashcat --example-hashes -m 27700 | grep Example.Hash | grep -v Format | cut -b 25- > tmp.hash.27700
|
||||
# $ ./hashcat --example-hashes -m 29800 | grep Example.Hash | grep -v Format | cut -b 25- > tmp.hash.29800
|
||||
#
|
||||
# 2. Now let it iterate through all -n values to a certain point. In this case, I'm using 200, but in general it's a value that is at least twice that of the multiprocessor. If you don't mind you can just leave it as it is, it just runs a little longer.
|
||||
#
|
||||
# $ export i=1; while [ $i -ne 201 ]; do echo $i; ./hashcat --quiet tmp.hash.27700 --keep-guessing --self-test-disable --markov-disable --restore-disable --outfile-autohex-disable --wordlist-autohex-disable --potfile-disable --logfile-disable --hwmon-disable --status --status-timer 1 --runtime 28 --machine-readable --optimized-kernel-enable --workload-profile 3 --hash-type 27700 --attack-mode 3 ?b?b?b?b?b?b?b --backend-devices 1 --force -n $i; i=$(($i+1)); done | tee x
|
||||
# $ export i=1; while [ $i -ne 201 ]; do echo $i; ./hashcat --quiet tmp.hash.29800 --keep-guessing --self-test-disable --markov-disable --restore-disable --outfile-autohex-disable --wordlist-autohex-disable --potfile-disable --logfile-disable --hwmon-disable --status --status-timer 1 --runtime 28 --machine-readable --optimized-kernel-enable --workload-profile 3 --hash-type 29800 --attack-mode 3 ?b?b?b?b?b?b?b --backend-devices 1 --force -n $i; i=$(($i+1)); done | tee x
|
||||
#
|
||||
# 3. Determine the highest measured H/s speed. But don't just use the highest value. Instead, use the number that seems most stable, usually at the beginning.
|
||||
#
|
||||
|
Loading…
Reference in New Issue
Block a user