hashcat keeps ending with "killed"
#1
Hello!

Firstly, I saw the thread: https://hashcat.net/forum/thread-4642.html , where the conclusion was that OP ran out of memory. Hope it's not a duplicate, if it is, I'm sorry in forward!
I use hashcat v3.60 on a GTX 980 rig, with newest nvidia driver, on a Ubuntu machine. It worked flawlessly for years, with different hashes and modes.
Now I tried a RAR3 type hash (-m 12500), which I got with rar2john from the rar file, edited a little, so it won't cause line length exception.
Now I tried it with different modes, but always ends with "Killed" error.
Previous thread concluded it was because of insufficient memory, but he tried loading thousands of hashes, while I only worked with one (also he used much older version of hashcat).
I have 2 gigs of memory (I know it is not much), and it always was sufficient for my cracking rig.
Is it possible, that there is another cause for the error?
I know upgrading RAM isn't a big deal nowadays, but our rig is stored remotely, so reaching it and upgrading takes quite some effort, that's why I wanted to ask here before!

Thanks in forward!


Messages In This Thread
hashcat keeps ending with "killed" - by xkcd3301 - 10-22-2017, 04:01 PM