![]() |
Public Hash Cracker programming help - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Misc (https://hashcat.net/forum/forum-15.html) +--- Forum: General Talk (https://hashcat.net/forum/forum-33.html) +--- Thread: Public Hash Cracker programming help (/thread-1286.html) |
Public Hash Cracker programming help - fizikalac - 06-13-2012 Hello, I need some code and database optimization tips. I'm trying to make a custom public hash cracker, just for LinkedIn hashes. Functions: - adding multiple passwords to the database at once - downloading all uncracked hashes - downloading cracked password list I already did a beta version in PHP and MySQL, but database calls are really slow. They take about 4 seconds each, because the database has 6.5 million rows. My VPS server: - Ubuntu server x64 - Intel i7 2,93GHz (1 core only) - 2GB RAM Database table: - id - INT(11) - sha1 - VARCHAR(40) - plain - TEXT The current SQL query for adding passwords is: PHP Code: UPDATE linkedin SET plain='".$plains[$i]."' WHERE substring(sha1,6,40) LIKE substring(SHA1('".$plains[$i]."'),6,40) *the query gets executed in a for loop for each new password, is there a faster solution? What can i do to optimise my application? Thank you so much! RE: Public Hash Cracker programming help - Hash-IT - 06-13-2012 Well done for getting this far fizikalac. I am really looking forward to this, I can't wait to get it going. I have been storing up my founds for a good few days now !! ![]() I know a few others who will join in when its up, we are all waiting in the background ! RE: Public Hash Cracker programming help - undeath - 06-13-2012 deliver hourly cached data. Are you sure there is no SQLi in there? Also using = instead of like. You also could try not to store the hashes in hex. RE: Public Hash Cracker programming help - fizikalac - 06-13-2012 (06-13-2012, 09:54 PM)undeath Wrote: deliver hourly cached data. Are you sure there is no SQLi in there? Also using = instead of like. You also could try not to store the hashes in hex. Thanks! = instead of LIKE was really an obvious one ![]() RE: Public Hash Cracker programming help - Xanadrel - 06-15-2012 Use 5 int columns to store the hashes. |