From 16615a55f173ec72f1a4b76ea6dd40a55fdb9109 Mon Sep 17 00:00:00 2001 From: GRMrGecko Date: Wed, 17 Sep 2014 15:35:56 -0500 Subject: [PATCH] Learned that the LinkedIn hash list had some things done to obscure the hash some. I changed the code to work with the obscured hashes. --- code/api.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/api.php b/code/api.php index a6cd57e..b4d6760 100644 --- a/code/api.php +++ b/code/api.php @@ -186,7 +186,7 @@ if ($_MGM['path'][1]=="email") { } else if ($_MGM['path'][1]=="hash") { connectToDatabase(); if (!empty($_REQUEST['sha1'])) { - $entries = databaseQuery("SELECT * FROM `sha1` WHERE `hash`=%s", $_REQUEST['sha1']); + $entries = databaseQuery("SELECT * FROM `sha1` WHERE `hash`=%s OR `hash`=%s", "00000".substr($_REQUEST['sha1'],5), $_REQUEST['sha1']);// The LinkedIn hashes seemed to have the first 5 characters replaced with 00000 because the person who uploaded on torrent sites decided that they didn't want to share the real hash. $entry = databaseFetchAssoc($entries); if ($entry!=null) { ?>

Password was stolen by hackers via .