You could be lucky since the data itself that is stored was not changed directly (actually never changed for years, exactly for "compatibility reasons"... but see reason for updated versoin below), see changes (blame log):
https://github.com/hashcat/hashcat/blame...1786-L1799
The problem mainly is that hashcat 6.0.0 has many new options and some command line arguments also changed a little bit etc and therefore they might be not compatible. That is why the development team decided to bump up the minium .restore format number required to 600:
https://github.com/hashcat/hashcat/commi...4c52555R18
The details about the .restore format can be found here:
https://hashcat.net/wiki/doku.php?id=restore#screenshot
and to change some options (for advanced users only, need to use the perl interpreter), you could try to use this:
https://github.com/philsmd/analyze_hc_restore
(the perl file that you need to download and run is https://raw.githubusercontent.com/philsm...restore.pl)
before making any changes to the .restore file, I would of course recommend to make backups of the files (maybe even of the whole old hashcat folder including wordlist hashes etc). and only afterwards begin to tamper with the .restore file.
What needs to be changed for sure is the restore format number, the hashcat binary paths and command (even cwd might need to be changed, depending on the local paths you use).
the binary for instance also changed from hashcat64.exe to hashcat.exe (or hashcat64.bin to hashcat.bin on linux)... all these changes need to be reflected also in the updated .restore file
with this code you will get all the options:
with this command you will see all the options:
again, this should normally only be used by advanced users and it might be dangerous if you don't have backups of your .restore files.
https://github.com/hashcat/hashcat/blame...1786-L1799
The problem mainly is that hashcat 6.0.0 has many new options and some command line arguments also changed a little bit etc and therefore they might be not compatible. That is why the development team decided to bump up the minium .restore format number required to 600:
https://github.com/hashcat/hashcat/commi...4c52555R18
The details about the .restore format can be found here:
https://hashcat.net/wiki/doku.php?id=restore#screenshot
and to change some options (for advanced users only, need to use the perl interpreter), you could try to use this:
https://github.com/philsmd/analyze_hc_restore
(the perl file that you need to download and run is https://raw.githubusercontent.com/philsm...restore.pl)
before making any changes to the .restore file, I would of course recommend to make backups of the files (maybe even of the whole old hashcat folder including wordlist hashes etc). and only afterwards begin to tamper with the .restore file.
What needs to be changed for sure is the restore format number, the hashcat binary paths and command (even cwd might need to be changed, depending on the local paths you use).
the binary for instance also changed from hashcat64.exe to hashcat.exe (or hashcat64.bin to hashcat.bin on linux)... all these changes need to be reflected also in the updated .restore file
with this code you will get all the options:
Code:
perl analyze_hc_restore.pl hashcat.restorewith this command you will see all the options:
Code:
perl analyze_hc_restore.pl --helpagain, this should normally only be used by advanced users and it might be dangerous if you don't have backups of your .restore files.