Updating Script - Security question

I know how to communicate between a script and updater.

I had been planning on giving a box with the new scripts to the customer, then they rez gadget and box and boom scripts get up dated.

I've seen a bunch of updaters work that way, problem is I don't want to give people a free set of scripts if they don't own the original device.

Now all scripts come nomod and nocopy and I think I could address this by only allowing them to run in prim I created but I was thinking there might be a more elegant way to do this. I just can't think of one.

I have no plans to go outside game to use external servers.

If you are doing an update server, I highly recommend no-transfer, not no-copy. That way you only have to check WHO you're giving to, not remember what you've given them in the past. Simplifies things quite a bit.

Just my two cents.

assuming you use different script pins for different products it really shouldn't be too big a deal, but if you want to be sure the person isn't stripping one set out first before updating them, then you could have the first script given check for the presence of the other scripts (possibly including check calls back and forth with those scripts) that should be there, then set a new pin if they are... all further transfers to be done with the new pin. that will also eliminate people scanning for the pin to use to replace scripts

Maybe this PIN idea is what I am missing.

I have read, re-read and read the descriptions of the LSL functions [using/creating PIN] but what they do escapes me. Thats partly the reason for this thread.

I know I am missing something simple but I can't figure out what.

set script pin
sets an access number that must be used by any script attempting to remotely load an active script into that prim. if it's the wrong number it'll fail.

remote load
works like give inventory, with a password (the script pin). used to give an active script to a prim, if the given script has the same name as an existing script in the target prim, it will replace it.

PIN actually stands for Personal Identification Number (just like on a bank debit card) and works like a password, if you have the password, you can place active scripts in the object, if not...

basic workflow goes like this
object A, is your scripted commercial object
somewhere in there it sets the pin/pw

object B is your scripted updater, that has new scripts to transfer (these can be set to not running)

rez object A
rez object B
B checks for presence of A, makes sure it has the same owner
B then transfers the new scripts to object A
those new scripts will replace the old ones if they have the same name, otherwise you may want a script in there that removes the old ones.

That means I could set the updater to nomod, thus preventing anbdoy remving the scripts manually ?

Removing modify permissions does not prevent the deletion or removal of scripts. Annoying but true.

The solution i use is that the purchased item must be used to signal that the updater be given in the first place. If they don't own the item, they can't request the updater.

That sounds like a good solution, rez the device and say update