Originally Posted by aldostools
The data generally is aligned to 4 and in less cases it is aligned to 1. An optimization that you could consider to implement in future releases is to test first the "offsets" aligned to 4, then repeat the loop for offsets aligned to 2 (and not aligned to 4), and loop again for the odd offsets. Also a start-stop range for offsets would be nice. 
|
Yeah, I know about this. But I didn't plan to use a bruteforce feature, I implemented it as just a proof on concept which shows the fact that keys can be bruteforced.
Originally Posted by aldostools
I have noticed that if only PARAM.SFO is listed, the pfdtool does not find the key using that file (maybe the key is not needed)
|
Yeah, the key for PARAM.SFO as well as for trophy files set at firmware files. Besides that PARAM.SFO hashed with 3/4 keys at one time and game files are hashed with only one key (secure file ID).
Originally Posted by katananja
I have a problem qith the pfdtool, it just crashes if you use -v, here is what winDbg say about the crash dump.
|
It is because a proper error handling and informational messages (which will be displayed when you specify -v option) is not implemented yet. I'll do it in the future version.