07-18-2019, 12:01 PM
yep yep yep
that's how the algorithm works (and actually most of the microsoft-invented algos),
also see this perl module to understand the algo: https://github.com/hashcat/hashcat/blob/...600.pm#L26
btw: the perl module of course works "correctly" because the encode ("UTF-16LE", $word) doesn't try to be as fast as possible and respects all encoding rules for utf16le (while as mentioned above the kernel does not).
You can also try to test with something like NTLM and you will experience the same problems...
actually we should add this limitation to docs/limits.txt (can somebody request this on github ?) to mention this "problem" of not doing the utf16 conversion with all the complicated encoding rules on kernel because of performance issues and making the conversion very complex
that's how the algorithm works (and actually most of the microsoft-invented algos),
also see this perl module to understand the algo: https://github.com/hashcat/hashcat/blob/...600.pm#L26
btw: the perl module of course works "correctly" because the encode ("UTF-16LE", $word) doesn't try to be as fast as possible and respects all encoding rules for utf16le (while as mentioned above the kernel does not).
You can also try to test with something like NTLM and you will experience the same problems...
actually we should add this limitation to docs/limits.txt (can somebody request this on github ?) to mention this "problem" of not doing the utf16 conversion with all the complicated encoding rules on kernel because of performance issues and making the conversion very complex