philsmd

I just accidentally found this issue because I was troubleshooting another problem with JWT token parsing and "cracking"... and I just want to let you know that: 1. the password...

What is the full command that you use (all switches / arguments / parameters) ? I agree with @Chick3nman that it seems to be either a problem of your installation/setup...

if you have a local copy, you need to run it with a prefix of "./" e.g. something like `./hashcat --help` maybe try to clean up a little bit older...

Does it still say something about `/usr/share/hashcat/` ? do you use your operating system package manager to install it ? if you run it locally, it should not say anything...

What is the command you run ? What hash type ? Do benchmarks work for you (`--benchmark`) ? More details are necessary / important here. Thanks

Yeah, I wouldn't be against it. we added a few other parameters that have to do with the brain-server recently like `--brain-server-timer` that allows configuring the time between "backups"/writes etc....

Did you try to investigate this already ? It's probably good if there is some user that has such device/hardware and can mess around with. Or even ask the arm...

The sha256 variant (v 3) seems to be doable and worth to implement... but I'm not sure if this is still a very commonly used format/encryption. Maybe you can give...

There is one doubt that comes to my mind. What is `buffsize` ? is this a maximum size of the buffer ? If this was through the input could never...

thanks for the update. doesn't that mean that the python code (and now also my "translated" perl code) are not working / doing it correctly ? because they do not...