Implement correct toggle of non-default charsets chars like german Umlaute
#4
(08-31-2024, 02:46 PM)penguinkeeper Wrote: No, unfortunately. These kinds of multibyte characters aren't really supported at all by rules. They will still be hashed correctly but you couldn't do ä to Ä, for example

Well, it depends on the encoding whether they are multibyte or not, doesn't it?

So is should at least be possible to manually implement toggle for ISO-8859-15 and ISO-8859-1 - as they are extended ASCII and use 1Byte, right?

UTF8 and UTF16 use 2 bytes for the Umlaute. If I understand you correctly, rules do not allow something like "if byte n is x and byte n+1 is y replace x by a and y by b" at all, right ?


You say they are hashed correctly. Now I happened to read https://github.com/hashcat/hashcat/issues/2121
which says that the utf16 encoding which is part of ntlm hashing does not work realiably for non-ascii chars.
In the limits.txt there is still written that this is an issue for the optimized kernels and that the pure kernel is required to handle them correctly. This seems like a contradiction to what you said - or is the german Umlaute a special case which is handled correctly even by the optimized kernel because of its rather high relevance for passwords compared to other non-ascii symbols like emojis?

thank you.
Reply


Messages In This Thread
RE: Implement correct toggle of non-default charsets chars like german Umlaute - by fsdafsadfsdsdaf - 08-31-2024, 09:01 PM