![]() Say you want to sell a Product, that works with licensing. ![]() You sell a lot of licenses to the public, but suddenly, 10 people re-distribute it, as the source code is just there, nothing changed. Here is an example of some Obfuscated Code: What obfuscators are out there? When your code is Obfuscated, it is extremely hard to identify, and for newcomers, its impossible. There are multiple well known obfuscators for Lua, but I’ll just name a few. Syanpse Xen: Probably the most well known one, most likely because its associated with Synapse X, a common exploit. Synapse Xen focuses on Security, but can be slow. You also have to purchase the Exploit, Synapse X, to be able to use Synapse Xen. Ironbrew: Another very well known Obfuscator is ironbrew. Ironbrew has incredible Security, like Synapse, and it’s performance and speeds are very good as well. ![]() Generally, from what I have seen, most people consider Ironbrew as the best Obfuscator you can get your hands on. Luraph: Probably considered the worst out of the 3, Luraph is another Lua Obfuscator. It isnt remotely as secure as Ironbrew or Synapse Xen, and it isn’t as fast as Ironbrew either. Verdict: I wouldn’t really say there is a “winner” that much, but the best Lua Obfuscators are definitely Ironbrew and Synapse Xen. They both have their goods and bads, but they are definitely the best. Remember, Obfuscation isn’t 100 percent security. Honestly, it isn’t even really Security, it’s just making your code hard to identify, so your stuff can’t be re-distributed nearly as easily. ![]() The only official feature that ever offered pure security was Private Modules, but they are gone now. Hope this Guide for Obfuscation helped you out! You could technically hold your code on an External Server, but that goes beyond the expertise of most, and it also costs for Hosting. Security through obfuscation is not security at all. It lures developers into thinking their codebases are secure instead of addressing the architecture of their game and properly designing said implementation. It’s a band aid that accomplishes nothing. ![]() It shouldn’t matter that clients have access to client-side code when using a decompiler. You should be building a proper model that ensures every server-client is sensible, not simply obfuscating your current codebase. If someone wants to read your obfuscated code, they can. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |