Joined: Tuesday, 24 Feb 2009, 18:42 Posts: 4772 Location: CZ
azikker wrote:
It would be much easier and faster if the 3dm cracker would create a tool, which calculates the necessary CPU/hardware id string and patches the cracked file(s) accordingly before running the game.
This solution would also be future-proof, since the crack will work on future hardware configurations.
i am pretty sure its not that easy , nobody managed to do this for cpuCEG yet and this one is supposed to be even harder
Obviously, they have thought about that as well, so there must be a very good reason not to do that. I bet it has something do with the fact that they don't want some people to get what's going on inside their loader.
The guys at Denuvo are not stupid. They'll analyze the the loader as soon as it's released and VMProtect won't hinder them much.
Some of the Securom/Denuvo developers have scene background: It is known that some ex-crackers fom Fairlight went to Sony DADC and other copy protection companies after the warez scene raids in 2001 and 2004.
prudislav wrote:
i am pretty sure its not that easy , nobody managed to do this for cpuCEG yet and this one is supposed to be even harder
Injecting that code during runtime may be not possible but a tool that patches the binary offsets in the exe or dll the same way Sam2k8 and (probably) 3dm does it manually, should be not that difficult to create.
It would be much easier and faster if the 3dm cracker would create a tool, which calculates the necessary CPU/hardware id string and patches the cracked file(s) accordingly before running the game.
This solution would also be future-proof, since the crack will work on future hardware configurations.
i am pretty sure its not that easy , nobody managed to do this for cpuCEG yet and this one is supposed to be even harder
Is there any list of all cpuCEG protected games?
Anyway, I dont see why wouldnt it be possible to implement it that way but I guess 3DM (and others) dont want to release their own so called "debugging/reverse engineering tools" public. By avoiding that they will release only some ini files, the loader/launcher/cracked exe and some dll files and not all the necessary tools they used to make it possible. Simply logic says, if they did it on their own PCs (i bet they tested it on multiple PCs) it would mean that this should be 100% possible (automatically and manually) on our own PCs (ofc if we have all the necessary tools
Users browsing this forum: No registered users and 6 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
Forum rules
IRC (Chat)
Non-Steam FAQ
Register
Search
Login
| 
. . .
(better than Win7, 
Thank you! 
