Software protection system may cause minidump to fail

[GoogleCodeExporter]

Hi,

I love the CrashRpt library, and how easy it makes it to catch issues directly 
from a customer's machine.
 I have integrated this into a free software provided by our company, and it works perfectly.

However, I now want to integrate this into another commercial software, which 
uses a post-build step to wrap the executable with some software protection and 
licensing code (Eleckey is the name of the licensing software).

I just wanted to know, in case the licensing system injects it's code into the 
executable, wouldn't this throw the error report off? Since the PDBs are for 
the unprotected app, and the mini-dump would be for the protected one, wouldn't 
this fail to be useful?

In such a case, could you suggest any way to work-around this, other than 
removing the license protection layer?

Any suggestions would be welcome.

Thanks in advance,
Bharat

Original issue reported on code.google.com by zexspect...@gmail.com on 11 Dec 2012 at 7:05

[GoogleCodeExporter]

Eleckey support:

Hello,

Thank you for your interest in our product.
In our shell protection wrapper, the injection method needs to make
some modification to the PE header. And, you also have an option to
enable the code section encryption.

We suggest that you try ElecKey Integrator to wrap over your program
using the injection method, with the code section encryption disabled.
Please see the attached screenshot. Please let us know if this can
work with your crash report.

Alternatively, you can use the provided KeyCheck API to integrate the
software protection and licensing system to your application. In this
case, there would be no problem with the crash report. There are a
lot of sample code available which you can study or reuse. Please
see in the ElecKey's folder:

\Examples\KeyCheck\VC\Simple\PCLicense_Instant\

If you have any question or need any assistance, please feel free
to let us know.

Best Regards,
Sciensoft Customer Support

Original comment by zexspect...@gmail.com on 13 Dec 2012 at 4:08

Attachments:

• CodeEncDis.jpg

[GoogleCodeExporter]

Closing this issue as there is a workaround (use API instead of injecting code 
into PE image).

Original comment by zexspect...@gmail.com on 14 Dec 2012 at 1:04

• Changed state: Done

[GoogleCodeExporter]

Hello zexspectrum,

Thanks a lot for all the support. Following up with the eleckey support
Forum was really thoughtful. I doubt even commercial library
 vendors do so much!

Thanks for everything!

Original comment by mallapur...@gmail.com on 16 Dec 2012 at 4:45