mirror of
https://github.com/hashcat/hashcat.git
synced 2024-11-22 08:08:10 +00:00
fixes #2121: explain the utf16-le / utf16-be limitation in docs/limits.txt
This commit is contained in:
parent
382c38cfab
commit
febb6692e0
@ -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
|
||||
##
|
||||
|
Loading…
Reference in New Issue
Block a user