I have a DLL that I intend to send to a third party and restrict it to run it safe Only if there is a specific USB device connected. I am using setupapi to call the SetupDiGetDeviceInstanceId () and get the serial number of the device.
I want to work hard to investigate the case of separation from DLL. For example, a simple call on SetupDiGetDeviceInstanceId is trackable and if someone wants to use my DLL without proper serial from the USB, then it can easily see its StraCamp in the assembly code and change it to (if Strcamp (...) == 0) to if (strcmp (...) == 1) .
What would be a good (and preferably "easy") approach to protecting my code against reverse engineering?
I think that as soon as it comes and you later It is cut off. I work to find a way to apply it in a "stupid proof" method often is reduced to work and in the end, annoying legal clients may inadvertently cripple the product. Rather than providing better support and constantly updating, better. Any security can be suppressed, so I would not spend too much time on it.
Comments
Post a Comment