Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I wonder how you can avoid users from tampering with the licence check in dynamic languages like javascript and ruby where anyone has access to the node_modules or rubygems directories.

I know this is not the focus of this particular product but since it has come up in multiple comments. How could this be solved?



It is also worth noting - how much do those cases really matter anyway? If they're going to the bother of disabling your licence checks, they probably aren't going to buy it anyway.


It's a fear that many have. When dealing with JavaScript based apps, where all of the source code is readable (more or less), there's really no way around the possibility of that happening. All you can do is require that updates and support require a license key. In the end, that will be a small amount of your users. Every software company deals with this issue a little differently.


Make it a super pain to mess with. Lace the code with license checks (different ones, not the same repeated) and run an obfuscator.

Works best with an external license server. If you have to be offline make the checks more involved.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: