Hashcat
Last updated
Was this helpful?
Last updated
Was this helpful?
For the Domain Cached Credentials 2 (DCC2
), the domain and username must be removed; only the value starting with $DCC2$
is required.
hashcat
includes a variety of effective rules in/usr/share/hashcat/rules
. can also be created.
If rule functions are on the same line, they are applied consecutively to each word.
If rule functions are on separate lines, each line is treated as a separate rule.
Enable a specific workload profile -> default is 2; use 3 if the PC focuses just on Hashcat.
Just passing the hash file (
$ hashcat example_hash
) will have the hash type autodetected.
$krb5asrep$23$
18200
$krb5tgs$23$
13100
NTLMv2
5600
NTLM
1000
$krb5asrep$17$
32100
$krb5asrep$18$
32200
$krb5tgs$17$
19600
$krb5tgs$18$
19700
NTLMv2 (NT)
27100
$DCC2$10240
2100
MD5
500
13400
22921
Cracking time is determined by dividing the keyspace by the hash rate:
Keyspace is calculated as the character set raised to the power of the password length. For example, with lowercase (26
), uppercase (26
), and digits (10
), the character set totals 62
. A five-character password would have 62^5
possible combinations.
The hash rate is a measure of how many hash calculations can be performed in a second (1
MH/s equals 1,000,000
hashes per second).
Increasing password length increases cracking duration by exponential time, while increasing password complexity (charset) only increases cracking duration by polynomial time.
Exponential time grows much faster than polynomial time.
Polynomial time (e.g., n2n^2n2, n3n^3n3): As input
nnn
increases, the number of steps grows at a manageable rate.Exponential time (e.g., 2n2^n2n, 3n3^n3n): The number of steps doubles, triples, or grows even faster with each increase in
nnn
, making it impractical for large inputs.
KeePass
()
$sshng$6$
()