@juiweasley: your cli is wrong, it is simpler than that, see my cli
depends, did you named your session and if not, did you startet by now another cracking task with hashcat?
problem, hashcat names the sesssion per default to hashcat and stores a file called hashcat.restore, without naming your session, these restore file is overwritten any time you start a new cracking task
you could restore any session by simple running
you can replace hashcat by any sessionname where a [sessionname].restore file exists
depends, did you named your session and if not, did you startet by now another cracking task with hashcat?
problem, hashcat names the sesssion per default to hashcat and stores a file called hashcat.restore, without naming your session, these restore file is overwritten any time you start a new cracking task
you could restore any session by simple running
Code:
hashcat --session=hashcat --restore
you can replace hashcat by any sessionname where a [sessionname].restore file exists