DSP Robotics Support

Here is a keymaker, that uses input data in order to create a key. It's very draft. But it's useful if you'd like to combine your customer with their copy of app they buy. This is very simple protection, but should stop kids and unexperienced file sharers from doing bad things... because in serial number you could include theyr bank account, credit card number and so on.

Few notes.

I used two different data splitters, because on one hand - I don't know if crypted data may contain commas (which would break the decoding), and on the other hand... I don't know how to make ruby splitter for multiple lines.

Another thing here - there is "empty line" after decoding, otherwise it will not work. If you connect outputs to string primitives, and click on content inside that prims, you will notice, that input data has additional end line marker, while decoded - not.

It's the idea. Anyone would like to optimize or give their shot?

I've made a much more complicated protection.
I use the PayPal transaction ID and the HD serial (but change after a new disk format) to generate the code in "blue".
The protection does not run in green to prevent access to memory.

Plugins communicate with the server checking the paypal transaction ID in DB, then register the plugin (if found) and create the response key.
Offline form available too.

Key is stored in PC and every key is mac based and pay ID too.

I see no reason for making anything complicated. I could write long argumentation for my statement, but I do not wish to evoke discussion about protections; I've seen such in the past.

Let say, that I see such sort of protection as public indicator, that something is legal or not, and as a modus operandi to slow down the "grey zone" (slow down enough to give folks the time to read info?) and to create contrast between shades of grey. Plus - it is my personal preference to use it that way.

I'm rather interested in optimizing the solution posted above. Nothing else.

But - sure, feel free to post other working examples if you wish.

Updated version. I just realized, that pushing this through different prims may actually work.
In user data you can use empty spaces at the end, and commas inside (prim conversions avoided).

Trog - should I expect any trouble with this one?