1. you don't need http://www.md5hashgenerator.com/ to generate hashes. We know we find the ISO code of that particular char here: http://en.wikipedia.org/wiki/ISO/IEC_8859-2 and we use linux OS, therefore run:
$ echo -en "\x01\x51"|md5sum
e8XXX09320XXXX08fXX5bXXX98XXX9f1
I even listed the codes you need s.t you are able to double-check, in above post: Å‘ "\x01\x51" ...
2. ?1?1? should be what? I see three question mark there... this doesn't make sense
3. --hex-charset -1 151 is what? hex needs 2 digits per "symbol" (0-ff , is 0 - 255) right? I gave you the examples... why are you doing it completely different...?
4. the hash you get from md5hashgenerator.com is wrong... (as said may be different encoding etc...)
5. just read carefully my post above and you should understand what you are doing wrongly...
the masked hash you posted (8f5b1XXXXedd5XXXX5595aXXXXe4315d) seems to correspond to the html entity string (urldecoded from %26%23337%3B to & # 3 3 7 ; - w/o spaces) ... basically the string "& #337;" (w/o space) was hashed by that site AS-IS.
Try
$ echo -en "& # 3 3 7 ;" | md5sum # remove the spaces to reproduce
Well, this sounds like a bad joke. I know this is not (just) your problem (if the site tries to hash html entities) but at least you should double-check w/ md5sum!
Therefore, again... the problems (and this in particular) seem to *not* lie on hashcat's site but between keyboard and computer ... and/or the service for md5 generation that you use
Just kidding
$ echo -en "\x01\x51"|md5sum
e8XXX09320XXXX08fXX5bXXX98XXX9f1
I even listed the codes you need s.t you are able to double-check, in above post: Å‘ "\x01\x51" ...
2. ?1?1? should be what? I see three question mark there... this doesn't make sense
3. --hex-charset -1 151 is what? hex needs 2 digits per "symbol" (0-ff , is 0 - 255) right? I gave you the examples... why are you doing it completely different...?
4. the hash you get from md5hashgenerator.com is wrong... (as said may be different encoding etc...)
5. just read carefully my post above and you should understand what you are doing wrongly...
the masked hash you posted (8f5b1XXXXedd5XXXX5595aXXXXe4315d) seems to correspond to the html entity string (urldecoded from %26%23337%3B to & # 3 3 7 ; - w/o spaces) ... basically the string "& #337;" (w/o space) was hashed by that site AS-IS.
Try
$ echo -en "& # 3 3 7 ;" | md5sum # remove the spaces to reproduce
Well, this sounds like a bad joke. I know this is not (just) your problem (if the site tries to hash html entities) but at least you should double-check w/ md5sum!
Therefore, again... the problems (and this in particular) seem to *not* lie on hashcat's site but between keyboard and computer ... and/or the service for md5 generation that you use
Just kidding