Jens Steube
Jens Steube
So if it's really like that, than I understood it correctly from the beginning. In that case the best way to detect such a case would be to check current...
You can use hashcat in --stdout mode
Yeah, that works fine On 28.02.2017 23:19, redfast00 wrote: > > So I just pipe hashcat to hashcat then? (trying to avoid too small > workloads) > > — >...
Before I do, you know you can do this already? You can use combinator.bin with 2 files and write the output to file. Then run combinator.bin again with the new...
I'm sorry, it's dead. Note that cracking, depending on hash-mode, is up to 800% faster even on CPU only. There's almost no reason to continue using hashcat-legacy. OTOH, it would...
It's a problem with the LLVM in the runtime, so there's nothing we can do in hashcat. Best way to approach this is by using HIP on Linux.
HIP works fine on AMD stable WHQL drivers. Do not use beta drivers. Please do not forget to close this issue if fixed after drivers change.
As always, you can find beta binary build on hashcat.net/beta
Yes, if the original tool has this policy, it should be set to 8 as described.
The problem with keyfiles is that they are applied before the KDF. Each keyfile tried, in this scenario requested, would double the time it takes to compute a single password....