01-14-2021, 04:09 PM
not quite sure wheter rules accept hex as charset but it seems implemented as you can see here
https://github.com/hashcat/hashcat/issues/1580
https://github.com/hashcat/hashcat/commi...b65f8bf4eb
so it should be possible, all you have to know is the hex-equivalent for your chars
sXY Replace all instances of X with Y
german ä is 0xc3a4 so
should work but resulting in
some tries later
seems to work, but i had to save the rules files explicit in ANSI on windows, utf-8 was not working
resulting in admin > ädmin for example
you could also try playing around with
--encoding-from | Code | Force internal wordlist encoding from X | --encoding-from=iso-8859-15
--encoding-to | Code | Force internal wordlist encoding to X | --encoding-to=utf-32le
encoding is a hell for itself
https://github.com/hashcat/hashcat/issues/1580
https://github.com/hashcat/hashcat/commi...b65f8bf4eb
so it should be possible, all you have to know is the hex-equivalent for your chars
sXY Replace all instances of X with Y
german ä is 0xc3a4 so
Code:
sa\xc3a4
should work but resulting in
Code:
Cannot convert rule for use on OpenCL device in file ruletest.txt on line 1: sa\xc3a4
some tries later
Code:
saä
seems to work, but i had to save the rules files explicit in ANSI on windows, utf-8 was not working
Code:
hashcat -a 0 --stdout -r rule.txt pw.txt > test.txt
resulting in admin > ädmin for example
you could also try playing around with
--encoding-from | Code | Force internal wordlist encoding from X | --encoding-from=iso-8859-15
--encoding-to | Code | Force internal wordlist encoding to X | --encoding-to=utf-32le
encoding is a hell for itself