01-15-2018, 11:49 PM
Hashcat makes a strict distinction between rules (see https://hashcat.net/wiki/doku.php?id=rule_based_attack) and masks (https://hashcat.net/wiki/doku.php?id=mask_attack).
solace is currently using a hashcat mask file (.hcmask file, see https://hashcat.net/wiki/doku.php?id=mas...mask_files or https://hashcat.net/wiki/doku.php?id=fre..._mask_file) which by hashcat's definition doesn't really use rules.
On the other hand, if you want to mangle some base words with rules in attack mode -a 0 (dictionary attack, instead of mask attack), you could for instance use substitute/replace rules (sXY).
One limitation of this rule is that it only allows to replace one byte (0x00-0xff) with another byte (0x00-0xff)... if you instead need to replace the character ^ (0x5e) with ˆ (e.g. 0xcb 0x86, 2 bytes) than you can't use the substitute rule directly.
There are many possibilities to get around this limitation. A simple straightforward approach would be to just externally generate a word list that already has all those characters substitute... or pipe it into hashcat with an external tool.
It's also not easy for me to list here all characters that are affected by this replace "bug". I would say that the best approach also here would be to test a lot of characters directly with the affected software version (an old mist version?) and see which characters will be replaced and what the replacement character is.
solace is currently using a hashcat mask file (.hcmask file, see https://hashcat.net/wiki/doku.php?id=mas...mask_files or https://hashcat.net/wiki/doku.php?id=fre..._mask_file) which by hashcat's definition doesn't really use rules.
On the other hand, if you want to mangle some base words with rules in attack mode -a 0 (dictionary attack, instead of mask attack), you could for instance use substitute/replace rules (sXY).
One limitation of this rule is that it only allows to replace one byte (0x00-0xff) with another byte (0x00-0xff)... if you instead need to replace the character ^ (0x5e) with ˆ (e.g. 0xcb 0x86, 2 bytes) than you can't use the substitute rule directly.
There are many possibilities to get around this limitation. A simple straightforward approach would be to just externally generate a word list that already has all those characters substitute... or pipe it into hashcat with an external tool.
It's also not easy for me to list here all characters that are affected by this replace "bug". I would say that the best approach also here would be to test a lot of characters directly with the affected software version (an old mist version?) and see which characters will be replaced and what the replacement character is.