Faux copy protection

[jjschwartz]

I'm creating an application meant to be freely available to other University departments. I'm not interested in copy-protecting it per se, but I want to make sure that the attribution and credit are maintained. Right now, the splash screen, which is a .bmp, has all the credit information. That .bmp is compiled into the appication as a resource.

I understand that there are resource editors out there that can find the .bmp in the application and remove or replace it. Is there a way to prevent a resource editor for getting at the .bmp? Is there a way to check the status of certain pixels to make sure it hasn't been altered? Any other ideas how to implement this sort of protection?

Thanks in advance,
Jeff Schwartz

 

[buho]

CRC your BMP and check it at load time.

Or encrypt it before making the resource and decrypt it at load time before splashing it.

buho (A).