Copyright and licensing scripts - UGN Security Forum

Okay so I am about to start getting some of my scripts together to release into the world. Things people find useful like Topsites, News script with hybrid BBS for User comments, Internal site messaging system, IT help desk tkt system, and image upload/Thumbnail creator script.

I want to ensure these are tied to me forever and ever in that someone else can't claim my work as thier own.

I was thinking of a license file which calls home with a hash or key that the script would not work with out. This however could cost the user and myself bandwidth. Then I was thinking of running a series of hard to find variables through the script that check to make sure the (c) is still inplace where it needs to be. If it isn't the script breaks. Not quite sure yet how I will do it.

My question to the 2 of you who read all that is this. Do you know of a way to ensure your data you want to stay in a script does stay in there?

I also thought of having the user register at my site with some of thier server info and in the script...

Code

require('https://www.vanceconcepts/scripts/whateverscript/index.php?server_ip=111.111.111.111&domain=somesite.com&registered_id=id_in_here');

The variables would not be hardcoded but pulled for the cnfg.php file used to set up the script on first run.

Then On my site I could verify the request(maybe) vs who it came from. Then send back a key/hash and time stamp for

Code

if($todays_date => "$pre_set_date"){
//call vanceconcepts to ensure this is still legit and not a copy on a new server
}

So then those scripts will only work when your server is on. scripts given freely or sold? if sold opens you to liability. (potentially)

call backs are evil!

Yes I thought about that. You could have several licensing servers around the net, For good redundancy, I would require the following

a.) each server is in different datacenter
b.) Each data center uses a different carrier
c.) each center guarentees at least 90% uptime

I figure with those 3 policys in place with 3 servers to authetcate too, each updating the other with new hashes and such you would have a reliable layer of redundancy in place.

Quote:

Originally posted by Gizmo:
call backs are evil!

Yea whatever master pirate... I also plan to use this to update the code. Should be able to over write souce files of my scripts with updates using this same concept. This would allow a pay once update free business model. This could be an added value to long term customers. Could even be sold as an added feature for gold version or enterprise version.

You might think it is a bad idea but don worry gizzy, you will allways get free copies from me

I find that a little anal; no offense... But easy to do, with even "virtual hosting", just sign up with an account at 3 differant hosts and use the same domain name, then set a round robbin on your validation host (validate.vancecreations.com for example); i however find callbacks a waste of time, sell licensing, some "loose" software could be good for business when people see what it is/use it