Cracking SHA1(linkedin)
#7
you could use hashcat-legacy with your CPU from https://hashcat.net/files/hashcat-2.00.7z (deprecated, not supported anymore)  update: it seems that hashcat-legacy never supported -m 190... or just implement the change in a separate clone of the hashcat repository:

https://github.com/hashcat/hashcat/blob/...a3.cl#L270
in all kernel files (a0, a1, a3).

Don't forget to remove the kernel cache directory kernels/ , otherwise your kernel changes wouldn't be loaded.



update: this is actually the old version I meant: https://web.archive.org/web/201606220055...clhashcat/ , https://hashcat.net/files/cudaHashcat-2.01.7z (CUDA NVIDIA), https://hashcat.net/files/oclHashcat-2.01.7z (OpenCL AMD), but of course there is no guarantee that these work on modern hardware and of course they are also not supported anymore by the dev team, nor maintained. so only use them at your own risk. It's probably better to just use latest version and add the change I pointed out above (+ kernel cache removal).
Reply


Messages In This Thread
Cracking SHA1(linkedin) - by whabikhazri - 08-10-2020, 05:41 PM
RE: Cracking SHA1(linkedin) - by royce - 08-10-2020, 05:45 PM
RE: Cracking SHA1(linkedin) - by whabikhazri - 08-10-2020, 07:05 PM
RE: Cracking SHA1(linkedin) - by philsmd - 08-10-2020, 07:07 PM
RE: Cracking SHA1(linkedin) - by royce - 08-10-2020, 08:45 PM
RE: Cracking SHA1(linkedin) - by whabikhazri - 08-11-2020, 01:43 AM
RE: Cracking SHA1(linkedin) - by philsmd - 08-11-2020, 09:57 AM
RE: Cracking SHA1(linkedin) - by whabikhazri - 08-11-2020, 05:25 PM
RE: Cracking SHA1(linkedin) - by mailmuncher2000 - 02-13-2021, 11:21 AM
RE: Cracking SHA1(linkedin) - by royce - 02-13-2021, 06:22 PM
RE: Cracking SHA1(linkedin) - by mailmuncher2000 - 02-14-2021, 01:06 AM
RE: Cracking SHA1(linkedin) - by mailmuncher2000 - 02-14-2021, 07:46 AM