From a7a3cf024e10ad3c50dc6f04ab957aea9fb5bcb1 Mon Sep 17 00:00:00 2001 From: Jens Steube Date: Tue, 15 Jun 2021 11:53:06 +0200 Subject: [PATCH] Update docs/limits.txt regarding UTF16 support in kernels --- docs/limits.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/limits.txt b/docs/limits.txt index 0ee928080..88024faec 100644 --- a/docs/limits.txt +++ b/docs/limits.txt @@ -26,6 +26,8 @@ It only means the filename itself. ## Hashing algorithms that internally use UTF-16 characters could in special cases lead to false negatives ## +For optimized kernels only (-O): Since hashcat v6.2.1 there's true UTF16 support for pure kernels: + 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). @@ -33,6 +35,8 @@ 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. +Since hashcat v6.2.1 there's true UTF16 support for pure kernels. + ## ## The use of --keep-guessing eventually skips reporting duplicate passwords ##