Weird result with MSSQL 2000 mode 131 - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-45.html) +--- Thread: Weird result with MSSQL 2000 mode 131 (/thread-8577.html) |
Weird result with MSSQL 2000 mode 131 - Mem5 - 08-18-2019 Hi, I have a MSSQL 2000 hash - mode 131 - This hash does NOT exist : 0x040016460666FF8664F8FF8F14400064F44FFF6FFF06044FF61FFF8664F8FF8F14400064F44FFF6FFF06044FF61F When cracked, hashcat v5.1.0 displays : 0x0400164606660000000000000000000000000000000000000000FF8664F8FF8F14400064F44FFF6FFF06044FF61F:password Not the same hash! Why does hashcat replaces the red part with zeros? Thanks! RE: Weird result with MSSQL 2000 mode 131 - undeath - 08-18-2019 A MSSQL 2000 hash consists of two hashes, one with the correct case and one with all upper case letters. Hashcat probably simply ignores one of them. see https://www.theregister.co.uk/2002/07/08/cracking_ms_sql_server_passwords/ RE: Weird result with MSSQL 2000 mode 131 - Mem5 - 08-18-2019 I wonder why it does not copy the hash itself in the result. Will read. Thanks. RE: Weird result with MSSQL 2000 mode 131 - atom - 08-22-2019 You're right, it should. I've never seen this block being filled with data (not being zero). Please create GitHub issue. |