09-25-2023, 10:58 AM
Hello,
I have a problem with hashes containing german special charaacters (äüößÄÖÜ Umlaute) and the Euro sign €.
1. For hashes with „only“ the umlaute that have been hashed as utf8 I use this way (example 5 character passwords) with hex-charset (because I did not get the included charsets work with utf8 hashes):
#german_umlaute.hcmask
c3,a4bcb684969c9f,?1?2?a?a?a?a
c3,a4bcb684969c9f,?a?1?2?a?a?a
c3,a4bcb684969c9f,?a?a?1?2?a?a
c3,a4bcb684969c9f,?a?a?a?1?2?a
c3,a4bcb684969c9f,?a?a?a?a?1?2
with:
$ echo -n ä | xxd -p
c3a4
ä c3a4
ü c3bc
ö c3b6
Ä c3 84
Ö c3 96
Ü c3 9c
ß c3 9f
Example: (macOS)
$ echo -n 1234ä | md5
0eXXc86d020ba6XXXXXXXXXXXXXX7a5d
$ hashcat -D1,2 -d3 -O -m 0 -a 3 0eXXc86d020ba6XXXXXXXXXXXXXX7a5d --hex-charset german_umlaute.hcmask
result:
0eXXc86d020ba6XXXXXXXXXXXXXX7a5d:1234ä
(
the includes charsets seem to work with converted to 8859-1:
echo -n 1234ä | iconv -f utf8 -t iso8859-1 | md5
16XX99c169d4b4XXXXXXXXXXXXXXa580
$ hashcat -D1,2 -d3 -O -m 0 -a 3 16XX99c169d4b4XXXXXXXXXXXXXXa580 -1 charsets/standard/German/de_ISO-8859-1.hcchr -2 ?a?1 ?2?2?2?2?2
result:
16XX99c169d4b4XXXXXXXXXXXXXXa580:$HEX[31323334e4]
$ echo 31323334e4 | xxd -r -p | iconv -f iso-8859-1
1234ä
)
2. For hashes with only the Euro sign €:
#euro.hcmask
e2,82,ac,?1?2?3?a?a?a?a
e2,82,ac,?a?1?2?3?a?a?a
e2,82,ac,?a?a?1?2?3?a?a
e2,82,ac,?a?a?a?1?2?3?a
e2,82,ac,?a?a?a?a?1?2?3
with :
$ echo -n € | xxd -p
e282ac
Example:
$ echo -n 1234€ | md5
e4XXb1726d37ecXXXXXXXXXXXXXXb397
$ hashcat -D1,2 -d3 -O -m 0 -a 3 e4XXb1726d37ecXXXXXXXXXXXXXXb397 --hex-charset euro.hcmask
result:
e4XXb1726d37ecXXXXXXXXXXXXXXb397:1234€
3. If I have a hash containing both german special characters (Umlaute) and the Euro sign, the 4 custom charsets are not enough because I would need 2 charsets for the Umlaute and 3 for the Euro. I could mix all the hex code in one or two charsets, but that would be very expensive.
So my question: Is a solution for this problem or a different approach?
Best would be a simple solution with a charset that supports UTF8 hashes but I did not get this working I guess because of the 4 or more hex digits per character.
Thanks
ManuB1G
I have a problem with hashes containing german special charaacters (äüößÄÖÜ Umlaute) and the Euro sign €.
1. For hashes with „only“ the umlaute that have been hashed as utf8 I use this way (example 5 character passwords) with hex-charset (because I did not get the included charsets work with utf8 hashes):
#german_umlaute.hcmask
c3,a4bcb684969c9f,?1?2?a?a?a?a
c3,a4bcb684969c9f,?a?1?2?a?a?a
c3,a4bcb684969c9f,?a?a?1?2?a?a
c3,a4bcb684969c9f,?a?a?a?1?2?a
c3,a4bcb684969c9f,?a?a?a?a?1?2
with:
$ echo -n ä | xxd -p
c3a4
ä c3a4
ü c3bc
ö c3b6
Ä c3 84
Ö c3 96
Ü c3 9c
ß c3 9f
Example: (macOS)
$ echo -n 1234ä | md5
0eXXc86d020ba6XXXXXXXXXXXXXX7a5d
$ hashcat -D1,2 -d3 -O -m 0 -a 3 0eXXc86d020ba6XXXXXXXXXXXXXX7a5d --hex-charset german_umlaute.hcmask
result:
0eXXc86d020ba6XXXXXXXXXXXXXX7a5d:1234ä
(
the includes charsets seem to work with converted to 8859-1:
echo -n 1234ä | iconv -f utf8 -t iso8859-1 | md5
16XX99c169d4b4XXXXXXXXXXXXXXa580
$ hashcat -D1,2 -d3 -O -m 0 -a 3 16XX99c169d4b4XXXXXXXXXXXXXXa580 -1 charsets/standard/German/de_ISO-8859-1.hcchr -2 ?a?1 ?2?2?2?2?2
result:
16XX99c169d4b4XXXXXXXXXXXXXXa580:$HEX[31323334e4]
$ echo 31323334e4 | xxd -r -p | iconv -f iso-8859-1
1234ä
)
2. For hashes with only the Euro sign €:
#euro.hcmask
e2,82,ac,?1?2?3?a?a?a?a
e2,82,ac,?a?1?2?3?a?a?a
e2,82,ac,?a?a?1?2?3?a?a
e2,82,ac,?a?a?a?1?2?3?a
e2,82,ac,?a?a?a?a?1?2?3
with :
$ echo -n € | xxd -p
e282ac
Example:
$ echo -n 1234€ | md5
e4XXb1726d37ecXXXXXXXXXXXXXXb397
$ hashcat -D1,2 -d3 -O -m 0 -a 3 e4XXb1726d37ecXXXXXXXXXXXXXXb397 --hex-charset euro.hcmask
result:
e4XXb1726d37ecXXXXXXXXXXXXXXb397:1234€
3. If I have a hash containing both german special characters (Umlaute) and the Euro sign, the 4 custom charsets are not enough because I would need 2 charsets for the Umlaute and 3 for the Euro. I could mix all the hex code in one or two charsets, but that would be very expensive.
So my question: Is a solution for this problem or a different approach?
Best would be a simple solution with a charset that supports UTF8 hashes but I did not get this working I guess because of the 4 or more hex digits per character.
Thanks
ManuB1G