12-07-2018, 02:48 PM
(This post was last modified: 12-07-2018, 03:14 PM by cryptolovi.)
[quote="philsmd" pid='43006' dateline='1544181928']
if I generate a md5 hash with your input $HEX[706f657a6965] I get a completely separate result:
The hash is wrong it's 'echo poezie|md5sum' (forgot the -n creating the hash for the commandline above). So it's searching for the wrong target at the example which I handcrafted. Sorry for posting a hash that might be confusing because the target is not known.
When I say I see the '?' it's not because of terminal translation issues but because I looked at the --stdout output. This option I can't use when giving the hash on the commandline. So, ok the handcrafting of the example errored. But the point still stands I think
For example the hexdump output of --stdout with the options --encoding-to 'ASCII//TRANSLIT' only (using a one word dictionary and the correct hash)
00000000 35 34 35 33 34 35 34 61 32 35 33 66 38 38 34 30 |5453454a253f8840|
00000010 38 31 31 61 66 33 32 63 38 36 64 32 30 30 65 34 |811af32c86d200e4|
00000020 0a 70 6f 3f 7a 69 65 0a |.po?zie.|
00000028
When using --encoding-from too on a dict file it gets a bit more complicated and error prone and you will get translations to;
0a 70 6f 3f 3c 3c 7a 69 65 0a |.po?<<zie.|
when the dict type is wrong (but will leave that out of scope since that's not what I'm questioning)
if I generate a md5 hash with your input $HEX[706f657a6965] I get a completely separate result:
Code:
printf "po\xebzie" |iconv -f "iso8859-1" -t "ASCII//TRANSLIT" | md5sum
5453454a253f8840811af32c86d200e4The hash is wrong it's 'echo poezie|md5sum' (forgot the -n creating the hash for the commandline above). So it's searching for the wrong target at the example which I handcrafted. Sorry for posting a hash that might be confusing because the target is not known.
When I say I see the '?' it's not because of terminal translation issues but because I looked at the --stdout output. This option I can't use when giving the hash on the commandline. So, ok the handcrafting of the example errored. But the point still stands I think
For example the hexdump output of --stdout with the options --encoding-to 'ASCII//TRANSLIT' only (using a one word dictionary and the correct hash)
00000000 35 34 35 33 34 35 34 61 32 35 33 66 38 38 34 30 |5453454a253f8840|
00000010 38 31 31 61 66 33 32 63 38 36 64 32 30 30 65 34 |811af32c86d200e4|
00000020 0a 70 6f 3f 7a 69 65 0a |.po?zie.|
00000028
When using --encoding-from too on a dict file it gets a bit more complicated and error prone and you will get translations to;
0a 70 6f 3f 3c 3c 7a 69 65 0a |.po?<<zie.|
when the dict type is wrong (but will leave that out of scope since that's not what I'm questioning)