![]() This means that the only way to deal with it was by reverse engineering EV Nova itself. As far as I can tell there is zero documentation about this encryption online, or at least zero surviving documentation. As you can see this is not easy to actually look at… even unencrypted binary data is not easy to look at, but this is especially not easy to look at. This means that liberal use of SheepShaver (a PPC emulator, for Classic Mac OS) is required. The API’s required were deprecated 10 years ago, and do not function correctly under 64-bit. Nothing on modern macOS will allow us to look at the contents of a resource fork easily. Good old ResEdit and Mac OS 9 to the rescue On top of that, if we parse the resources using these structures the data is completely garbled and insane due to the encryption. Yep, both resources have a different format internally, which means they can’t be read with exactly the same process. I have attached two screenshots beneath of the code structures representing the two NpïL resources. However I can not currently find it, so not able to link to it. There is a document online covering the actual data layout of the pilot resources (I believe by guy).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |