After trying your example, I came to the conclusion that you might have hit exactly one limitation of hashcat, i.e. that it doesn't perform a "perfectly correct" utf16 conversion of the password candidate but instead (for performance reasons) it sets the 2nd byte always to 0.
This is actually a known limitation and of course only affects the hash types which use utf16 within the algorithm.
I think there is currently no open issue on github (please double-check) about this limitation. Feel free to request this new feature (but of course, we need to think about its impact on the performance)
This is actually a known limitation and of course only affects the hash types which use utf16 within the algorithm.
I think there is currently no open issue on github (please double-check) about this limitation. Feel free to request this new feature (but of course, we need to think about its impact on the performance)