See https://hashcat.net/wiki/doku.php?id=mask_attack
First you define the custom charset:
-1 ?u?d
which means: define a custom charset (see https://hashcat.net/wiki/doku.php?id=mas...m_charsets ), to use upper letters and digits
then think about the length and define the mask:
?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1
this means: use the custom charset (defined in first step with -1) and use a length of 16 (hence 16 times ?1)
the full command then would be:
oclHashcat64.exe -m 0 -a 3 -1 ?u?d file_containing_the_hash.txt ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1
So now comes the bummer:
brute-forcing, or better said using a mask attack of length 16, is not (really) feasible.
Think about the keyspace, it would be (26 + 10) * (26 + 10) * ... * (26 * 10) = 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 or if you want 36 ^ 16 ( to the power of 16) =
7958661109946400884391936
Even an enormous huge rig wouldn't finish that keyspace very soon ;(
First you define the custom charset:
-1 ?u?d
which means: define a custom charset (see https://hashcat.net/wiki/doku.php?id=mas...m_charsets ), to use upper letters and digits
then think about the length and define the mask:
?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1
this means: use the custom charset (defined in first step with -1) and use a length of 16 (hence 16 times ?1)
the full command then would be:
oclHashcat64.exe -m 0 -a 3 -1 ?u?d file_containing_the_hash.txt ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1
So now comes the bummer:
brute-forcing, or better said using a mask attack of length 16, is not (really) feasible.
Think about the keyspace, it would be (26 + 10) * (26 + 10) * ... * (26 * 10) = 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 * 36 or if you want 36 ^ 16 ( to the power of 16) =
7958661109946400884391936
Even an enormous huge rig wouldn't finish that keyspace very soon ;(