Freakin
|
|
June 27, 2011, 08:10:44 PM |
|
So I found out I'm in the latest lulzsec release due to an old account on hackforums.net which they dumped teh whole DB from
Can anyone help me validate my hash/salt with possible passwords?
A given entry from the db leak is
,(69593, '[REDACTED]', 'eace3bb282ccf8e94c3deecca34387cd', 'Nc35cumy', 'jqU7rP8f72wSyaluRJWvASydPueY8pyGnIWHUTgQB4iAT1PVdb', '[REDACTED]', 7, 0, 0.00, NULL, NULL, NULL, 2, NULL, 0, NULL, 1245380456, 1280737988, 1280736651, 1280731356, NULL, 0, NULL, NULL, NULL, '13-1-1991', 'all', NULL, NULL, 1, 0, 0, 0, 1, 2, 0, 'linear', 1, 1, 1, 1, 0, 0, 0, NULL, NULL, -5, 1, 2, NULL, NULL, 3, 0, 0, 0, NULL, '1**$%%$2**$%%$3**$%%$4**', NULL, 58522, 0, 0, '70.127.62.142', '97.96.9.20', 1633683732, 1182744206, 'english', 28895, 1, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 0, NULL)
password hash is the 3rd entry and salt is the 4th entry, so eace3bb282ccf8e94c3deecca34387cd:Nc35cumy in this example (not my account obv)
I tried using the same perl crypt() script that I used for the Gox leak but it's not outputting a hash in the format I see in the leaked data.
Please help!
|