06-20-2016, 12:05 AM
Are you certain the conversion is done in pairs of hex characters (e.g. ff 0f => 25515), and not interpreting the entire 40-character sequence as one value and converting it?
e.g. instead of "f1d2d2f924e986ac86fdf7b36c94bcdf32beec15" being converted into (241210...), it'd be (138056...).
Otherwise, I think you're correct, and it's not unambiguously parseable. The cheesy way to work around this would be to write something that spits out all the valid ambiguous parses that could result in that string (which, in some cases, might only be one), and then try breaking those - presumably, if it's encoded the way you say it is, then cracking _any_ of those hashes should work, since they encode to the same end result.
e.g. instead of "f1d2d2f924e986ac86fdf7b36c94bcdf32beec15" being converted into (241210...), it'd be (138056...).
Otherwise, I think you're correct, and it's not unambiguously parseable. The cheesy way to work around this would be to write something that spits out all the valid ambiguous parses that could result in that string (which, in some cases, might only be one), and then try breaking those - presumably, if it's encoded the way you say it is, then cracking _any_ of those hashes should work, since they encode to the same end result.