Control access of resources from executable package

The final product of an executable package with resources is the executable and a bundle file, which can be easily accessed by anyone. Is there any way to prevent the user from accessing the bundle's content? Would I have to encrypt the files or something like that?

What’s your goal of preventing the user from accessing these resources? Almost by definition this is a DRM scheme — you’re giving the user some data but you want to restrict how they use that data — and DRM schemes are… well… tricky.

This issue crops up regularly on DevForums, for example, this thread.

Share and Enjoy

Quinn “The Eskimo!” @ DTS @ Apple

1 Like

Thanks for the resources! I was just wondering what one could do to distribute an application that relies on some json file, for example, while preventing someone of get the file and use it outside without giving credits to the author.

Terms of Service

Privacy Policy

Cookie Policy