+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html)
+--- Forum: Old oclHashcat Support (https://hashcat.net/forum/forum-38.html)
+--- Thread: parsing restore file (/thread-3302.html)
parsing restore file - richk - 04-14-2014
Has anyone parsed the restore file into python ctypes? I'm having problems doing so.
Since I thought it was a an issue with my knowledge of ctypes I posted the issue on StackOverflow here (code included): http://stackoverflow.com/questions/23021250/access-to-ctypes-argv-from-binary-file-through-python
but didn't have any luck with getting a solution worked out. My code will parse the restore file, but my problem is with items like argv. Any idea how to parse that properly in Python?
RE: parsing restore file - atom - 04-15-2014
note that the restore structure changes massively with v1.20.
also see this:
https://hashcat.net/forum/thread-3047.html
RE: parsing restore file - richk - 04-15-2014
(04-15-2014, 06:13 PM)atom Wrote: note that the restore structure changes massively with v1.20.
also see this:
https://hashcat.net/forum/thread-3047.html
Understood. I can adjust accordingly when the next version is released. However, the confusion for me remains. Even in the next version the wiki indicates that the restore file format will store argv values as a **argv type. This is confusing for a restore "file" since pointers don't really make sense in a file. In the code I posted previously the only way I could figure to read the argv values is to read the text after the initial structures 328 bytes. I'm not critiquing; this is more my problem than the implementation. I'm just trying to understand the best way to parse the restore file values so I can integrate oclHashcat with the system I'm building.
RE: parsing restore file - richk - 04-15-2014
My other question is that it seems like there is much less information in the projected 1.20 (1.02?) version of the restore file. Is there going to be a way to get status updates on information like the number hashes cracked, GPU temps, etc. Basically, it would be great if there were a way to access the same status information you normally get from stdout programmatically. I think many would like to integrate oclHashcat into a larger system, but without an API or some way to interface it's hard to do so.
I understand this is a free program, and an awesome one at that. These are just some thoughts since it applies to what I'm working on.
RE: parsing restore file - atom - 04-16-2014
oclHashcat v1.20 has a new parameter that will help you integrating called --status-automat that you can simply read from stdout
RE: parsing restore file - richk - 04-16-2014
Oh very cool..I guess I'll to make due until the new release then. Thanks!
RE: parsing restore file - richk - 04-16-2014
Just so you're aware I'm planning on writing a full python wrapper for oclHashcat once it's easier to get stats in the next version. I have a wrapper now, but it's not good enough for general release imo. It sounds like the next version will have the interfaces available that I need to write a better one.