11-21-2017, 05:58 PM
You do not need --hex-salt. This has nothing to do with salts.
If anything you would need --hex-charset, but that is not necessariy and only needed if you define a custom charset (-1, -2, -3 or -4) or a custom mask.
The only thing you need is the information of the encoding.
Hashcat even has a --encoding-to and --encoding-from option to facilitate the conversion between different encodings.
If your password seems to be only 1 character long, it doesn't mean that it only uses 1 byte. Depending on the character encoding, only a very few characters (the most common for that specific language) are encoded with 1 byte.
Therefore, a password that only consist of 1 character could be using multiple bytes and hashcat (and all underlying hashing algorithms) work with bytes (therefore the length that hashcat shows e.g. in mask attack is always showing the bytes, not the characters).
I think you should try different encodings and try to understand character encoding.
If anything you would need --hex-charset, but that is not necessariy and only needed if you define a custom charset (-1, -2, -3 or -4) or a custom mask.
The only thing you need is the information of the encoding.
Hashcat even has a --encoding-to and --encoding-from option to facilitate the conversion between different encodings.
If your password seems to be only 1 character long, it doesn't mean that it only uses 1 byte. Depending on the character encoding, only a very few characters (the most common for that specific language) are encoded with 1 byte.
Therefore, a password that only consist of 1 character could be using multiple bytes and hashcat (and all underlying hashing algorithms) work with bytes (therefore the length that hashcat shows e.g. in mask attack is always showing the bytes, not the characters).
I think you should try different encodings and try to understand character encoding.