I would like to receive the most recent news.
My e-mail is:


Subscribe
FORUM
Forum: Technical questions Back to forum list

Integration with Exeprotector
Imran 12 Dec 2006 6:51:32

Hi,

We have a program written in Borland C++ builder and want to protect it. However, we do NOT want to add any code referring to ExeProtector in our code. I want to know what are the disadvantages. In other words, we want to create a secured version of our .exe file without changing or recompiling our original binary.

Does that guarantee:

1. That no one will be able to debug it?
2. That no one will be able to create our serial numbers?
#1590
Matthew 15 Dec 2006 4:22:12
Assuming you mean EXECryptor and not ExeProtector, then you’ll be losing most of the advantage if you don’t add the markers to your code. The whole point is that you should encrypt the code that checks the serial numbers so that people cannot reverse engineer or modify the code to skip the test. The markers that get included are "inert" so if you don’t apply the protection then it still works.

I guess there will be anti-debug code if you don’t use the markers, but the biggest benefit is lost.

(I’m just a user, not from Strongbit.)
#1603
StrongBit Team 20 Dec 2006 0:27:28

Hi,

Imran wrote
In other words, we want to create a secured version of our .exe file without changing or recompiling our original binary.


Such protection scheme is call "attached protection" and it is less secure than protection with SDK.

1. To debug application attacker need to bypass all anti-debug features, so debugging with common debuggers is impossible.
2. If you don’t use serials from EXECryptor then we can’t guarantee anything.

Regards,
StrongBit Team
#1632


If you would like to post a question, reply or comment on our general forum you have to be registered. Please register for free and login here

 
Copyright © 1998-2018 StrongBit Technology Terms of Use and Privacy Statement