1 hour ago
Thank you for your answer and link. From reading it, this part seems to relate to what you're saying: "Therefore it is safe to store only 128 bits of it in a lookup database in hashcat. That means even for SHA512 with 512 bits, we are actually only interested in 128 bits of it. That is great, so we only need to test for 128 bits instead of 512 bits and save some clocks."
So from this and other info from that link, am I right to understand that basically it is a freak accident where the 128 bits tested match the hash from my list except for that specific part that isnt tested and should match? If so then there is just no solution and the hash is just corrupted and not linked to any real password?
Or is there a way to test a different "position" of those 128 bits (that would include the different character)?
So from this and other info from that link, am I right to understand that basically it is a freak accident where the 128 bits tested match the hash from my list except for that specific part that isnt tested and should match? If so then there is just no solution and the hash is just corrupted and not linked to any real password?
Or is there a way to test a different "position" of those 128 bits (that would include the different character)?