Hashcat not actually cracking the hash
#2
Well lets cover some basics.

1. You are using The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali). Don't do that. As you'll have hopefully noticed, even the forum will automatically replace it's name with a more proper name. It doesn't handle hashcat well because it's a cluster fuck of other tools and it does not play nice with the OpenCL runtimes we need. Don't use it for hashcat and your life will be better. Just run hashcat on your Windows, it doesn't care and runs just as well on Windows as Linux.

2. You are using --force. The requirement for usage of --force is often due to a hashcat breaking problem with your installation. If you ran without it you probably got the following message: "You can use --force to override this, but do not report related errors." Let's read that message carefully a few times and make sure we understand it properly.

3. Optional: Don't run hashcat in a VM, especially if you plan to use GPUs. VMs and GPUs are annoying to get to play nicely together so just skip it and save yourself some headaches.

If your professor is telling you to use --force and/or run hashcat on Ka-li, you may want to point him to some of us so we can update him on best practice with hashcat. We've been telling people what to and what not to do for a while and yet, for some reason, it doesn't really seem to stick.
Reply


Messages In This Thread
RE: Hashcat not actually cracking the hash - by Chick3nman - 04-23-2019, 04:56 AM