ayozzhero
Well-known member
To combat software piracy, I've decided to try dongle protection. I've bought the trial kit and found out no source code given but the API.
Using API is ok, but what comes to my mind is... the API can be easily replaced by a fake API. For example, let's say the API is called dongle.dll. And there is a function in the dll called ScanDongle() which returns 0 for dongle not present and 1 for dongle present.
I think, it won't be difficult for a programmer to code a fake dll with the same function name and return and integer value of 1 when the function is called. Hence, the dongle will be no longer needed. (I haven't tried it yet, but I think it is implementable)
Will it be harder to crack if I have the source code myself and include it in the EXE file instead of a dll? or dongle protection is only a marketing gimmick?
If you have any idea or opinion, you're most welcome to contribute to combat piracy.
Using API is ok, but what comes to my mind is... the API can be easily replaced by a fake API. For example, let's say the API is called dongle.dll. And there is a function in the dll called ScanDongle() which returns 0 for dongle not present and 1 for dongle present.
I think, it won't be difficult for a programmer to code a fake dll with the same function name and return and integer value of 1 when the function is called. Hence, the dongle will be no longer needed. (I haven't tried it yet, but I think it is implementable)
Will it be harder to crack if I have the source code myself and include it in the EXE file instead of a dll? or dongle protection is only a marketing gimmick?
If you have any idea or opinion, you're most welcome to contribute to combat piracy.