10-08-2012, 05:58 AM
10-08-2012, 06:08 AM
appears to be salted md5, but it's impossible to know precisely which algorithm was used to create it without knowing where it came from or having the source. could be md5(salt.pass), md5(pass.salt), md5(md5(salt).pass), md5(md5(salt).md5(pass)), so on and so forth. you'll have to use exhaustive trial-and-error unless you can determine its origin.
10-08-2012, 08:02 AM
(10-08-2012, 06:08 AM)epixoip Wrote: [ -> ]appears to be salted md5, but it's impossible to know precisely which algorithm was used to create it without knowing where it came from or having the source. could be md5(salt.pass), md5(pass.salt), md5(md5(salt).pass), md5(md5(salt).md5(pass)), so on and so forth. you'll have to use exhaustive trial-and-error unless you can determine its origin.
I found this hash from Oracle 10g version, I guess it used the spring security algorithm to do the hash.
Is it helpful?
10-08-2012, 09:03 PM
it may have been in an oracle 10g database, but that's not an oracle 10g hash.
if it was hashed with Spring Security then it's likely md5(pass.salt)
if it was hashed with Spring Security then it's likely md5(pass.salt)
10-09-2012, 02:09 PM
This definitely looks like MyBB hash since both the hash and salt follow their usual format. The right algorithm for it is -m 2811 which md5(md5($salt).md5($pass)).
10-12-2012, 09:21 AM
thank you for your reply mastercracker. I have another hash that I can't find out what is the exact algorithm it used. Can you take a look at it?
Hash:
Lw7Qe2Cn+jI=
Hash:
Lw7Qe2Cn+jI=
10-12-2012, 10:11 AM
The char = on the end mostly points to Base64