Also, compiled code is much less likely to become corrupted over time.ĭata is the most valuable (in my opinion) - so consider protecting against employees who might like to take a copy of the db or of certain data to one of your competitors. ![]() But it will protect against a 'who' user who likes to meddle. Compiling won't protect against a 'who' code competitor because they either have the resources or the budget to decompile. You can compile code - to decompile is difficult, but there are services out there which will do it for a price. ![]() You can hide things - which will deter some people but not others who know how to unhide things. ![]() The first things you should be asking yourself is who are you protecting the db from, what in particular and why. The question(s) you are asking has been asked many many times before and there are many possible solutions, although none guarantee complete security.
0 Comments
Leave a Reply. |