DeforaNetworks/hashcat
3
0
Fork 0
Code Releases Activity

Merge pull request #2261 from philsmd/patch-3

Browse Source 
fixes #2121: explain the utf16-le / utf16-be limitation in docs/limits.txt
This commit is contained in:
Jens Steube
2020-01-03 11:42:39 +01:00
committed by GitHub
parent 382c38cfab febb6692e0
commit 469e13aa0b
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/limits.txt
+11
View File
@@ -22,6 +22,17 @@ Important: That does not mean UTF-16 file content, which is fully supported.
It only means the filename itself.
##
## Hashing algorithms that internally use UTF-16 characters could in special cases lead to false negatives
##
The UTF-16 conversion implementation used within the kernel code is very elementary and for performance
reasons does not respect all complicated encoding rules required to correctly convert, for instance, ASCII
or UTF-8 to UTF-16LE (or UTF-16BE).
The implementation most likely fails with multi-byte characters, because we basically add a zero byte every
second byte within the kernel conversion code.
##
## The use of --keep-guessing eventually skips reporting duplicate passwords
##