Patching file

[TechLord]

If you can share the files with me, then I will take a look.
The CRC check function for Wibu Codemeter is there mainly in the same file itself and the wrapper code does it.
So generally, the CRC checking function(s) have to be patched, to avoid "failing" the check.
In case of the Wibu's OWN files, like WibuCm32.dll for example, the runtime also checks the digital signatures, as does the Kernel component of the Wibu Codemeter.
Depending on the version of the Codemeter/AxProtector used, the pointer to the CRC of the file is found at a particular location.
See this post and the attached screenshots.

http://forum.exetools.com/showpost.php?p=100098&postcount=21

So you should ensure that the CRC always either comes out to the "passing" value at runtime, OR patch the checking function.

USUALLY this will suffice.

If the RUNTIME etc is checking the digital signature then it's a wee bit more complicated.

I can only say after I actually see the file.

[peterg70]

it would seem that axprotect has the capability of monitoring files outside the exe for modification.

Unwrapping and patching can be done on the exe but trying to avoid excessive work for no value.

So chasing patching the licensing DLL for flexlm. Patches work but software in exe detects the modification.

Like I said before someone else has managed to recalculate the hash by modifying 20 byte near the end of the file to make it not detect the modification.

What hashing of externallly protected files does axprotect have?