06-02-2016, 12:07 PM
Apologies for any confusion caused, and to the author at rurapenthe.me, I see now that I had somewhat misinterpreted the article. But it still doesn't have a solution for passwords with characters of variable length as far as I can see. Even for a UTF-8 encoded german password that's mostly made up of a-z (one byte) but may include ß (two bytes), you'd have to run many rules to cover this.
Isn't the only sane approach here to support wide character encodings in hashcat, all the way from character entry through to the kernels on the GPUs? I'm certainly not interested in running with ?s or ?S to try all specials in Unicode (I've not used either of those before). I'm specifying the charset with --custom-charsetX=<chars>.
I'm just surprised that a couple of UTF-8 encoded password like abc€ß and €bß hashed with a single sha1 seem to cause this much trouble. Or please let me know how to crack the hashes bed208c08c74a2ea4c5b1b29ffd46bd799821326 and c45088d56cf608d841b241dd755c2bee6a684e11 with hashcat. I can do it, but it requires lots of rules, and probably lots of invalid UTF-8 characters. Here's how I generated the hashes, in a plain Ubuntu 14.04 terminal session:
$ echo -n abcۧ | hexdump -C
00000000 61 62 63 e2 82 ac c3 9f |abc.....|
$ echo -n abcۧ | sha1sum
bed208c08c74a2ea4c5b1b29ffd46bd799821326 -
$ echo -n €bß | hexdump -C
00000000 e2 82 ac 62 c3 9f |...b..|
$ echo -n €bß | sha1sum
c45088d56cf608d841b241dd755c2bee6a684e11 -
You mention jtr, I was hoping to have more success with that as my next attempt. I'd be happy to receive any pointers, will try to read up on charsets/utf8 in jtr today.
Isn't the only sane approach here to support wide character encodings in hashcat, all the way from character entry through to the kernels on the GPUs? I'm certainly not interested in running with ?s or ?S to try all specials in Unicode (I've not used either of those before). I'm specifying the charset with --custom-charsetX=<chars>.
I'm just surprised that a couple of UTF-8 encoded password like abc€ß and €bß hashed with a single sha1 seem to cause this much trouble. Or please let me know how to crack the hashes bed208c08c74a2ea4c5b1b29ffd46bd799821326 and c45088d56cf608d841b241dd755c2bee6a684e11 with hashcat. I can do it, but it requires lots of rules, and probably lots of invalid UTF-8 characters. Here's how I generated the hashes, in a plain Ubuntu 14.04 terminal session:
$ echo -n abcۧ | hexdump -C
00000000 61 62 63 e2 82 ac c3 9f |abc.....|
$ echo -n abcۧ | sha1sum
bed208c08c74a2ea4c5b1b29ffd46bd799821326 -
$ echo -n €bß | hexdump -C
00000000 e2 82 ac 62 c3 9f |...b..|
$ echo -n €bß | sha1sum
c45088d56cf608d841b241dd755c2bee6a684e11 -
You mention jtr, I was hoping to have more success with that as my next attempt. I'd be happy to receive any pointers, will try to read up on charsets/utf8 in jtr today.