hkothari Posted February 4, 2010 Share Posted February 4, 2010 I know this is a complex topic and all, and you can't really protect your php software because in its executable from it's its source, but I was just wondering how companies require a key for their software to work like vBulletin for example? Like how do they require you to pay for it and have a key before you install it? Just curious. Thanks. Quote Link to comment Share on other sites More sharing options...
greatstar00 Posted February 4, 2010 Share Posted February 4, 2010 just use zend engine to convert your code so, they arent readable by human being so, u can ask someone for a key Quote Link to comment Share on other sites More sharing options...
oni-kun Posted February 4, 2010 Share Posted February 4, 2010 I know this is a complex topic and all, and you can't really protect your php software because in its executable from it's its source, but I was just wondering how companies require a key for their software to work like vBulletin for example? Like how do they require you to pay for it and have a key before you install it? Just curious. Thanks. VBulletin uses some annoying homecalls to prevent an enduser from installing it without a purchased key. Although it's just as easy to remove (effectively nullifying the homecalls) and get the software for no cost. My point isn't piracy, it's that that method is not secure in any means. Quote Link to comment Share on other sites More sharing options...
JonnoTheDev Posted February 4, 2010 Share Posted February 4, 2010 I know this is a complex topic and all, and you can't really protect your php software because in its executable from it's its source, but I was just wondering how companies require a key for their software to work like vBulletin for example? Like how do they require you to pay for it and have a key before you install it? Just curious. Thanks. You can't really stop people disributing open source code although you could ask for payment for the software and once you have received the monies send the user a download link where they will have to login to access, or just email a zipped package. One method to ensure that the software cannot be distributed is to ask the user for the domain where they will be installing your software. before you send the software to the user you could add somewhere in the code so it will only function on that domain. Once you have done this you could encrypt the codebase so it cannot be modified. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.