07-03-2014, 10:29 AM
Seems you didn't get it.
Therefore I will explain it again with an example:
sha1_hex (sha1 ($pass)) == the one you NEED
The one -m 4500 == Double SHA1 does (double means to take the hex and apply SHA1 again, not use the binary version and use SHA1 afterwards):
It is as I said above, a different algo (w/ different input) produces a different result.
-m 4500 uses the hex represenation, while the algo you need does not (it uses the non-ascii representation)
This algo that you need is currently not supported.
Therefore I will explain it again with an example:
sha1_hex (sha1 ($pass)) == the one you NEED
Code:
$ echo -en "A\x00B\x00C\x00" | sha1sum # first 'iteration'
a9b1640a163865c75b3a97c7f927750297a1969a
$ echo -en "\xa9\xb1\x64\x0a\x16\x38\x65\xc7\x5b\x3a\x97\xc7\xf9\x27\x75\x02\x97\xa1\x96\x9a" | sha1sum
c6876c05f745140f51a200f82159463c91b2522fThe one -m 4500 == Double SHA1 does (double means to take the hex and apply SHA1 again, not use the binary version and use SHA1 afterwards):
Code:
$ echo -en "A\x00B\x00C\x00" | sha1sum # first 'iteration'
a9b1640a163865c75b3a97c7f927750297a1969a
$ echo -n a9b1640a163865c75b3a97c7f927750297a1969a | sha1sum
cf26c5ff00eeec70ce091fc2e6e9114b6bf16cd2It is as I said above, a different algo (w/ different input) produces a different result.
-m 4500 uses the hex represenation, while the algo you need does not (it uses the non-ascii representation)
This algo that you need is currently not supported.