Correct me if i’m wrong, but this is what i have been told about the old and new encrypting methods:
V1 algorithm used a static key for encryption. Same source code get same encryption result.
V2 algorithm is improved a bit. Introduced dummy data generated by random seed to fill in head/tail of the result file. So the result file is always different even if the source is not modified.
mmm, there is really no point for me, to talk about .mse files.
My interest was only to prove myself how easy it is… nothing more… Just in case I decided to sale or release something…
I suppose many have or are currently trying… but if they can’t solve the problem, then it’s a waste of time to even think about it. IMO.
EDIT: just to add
And in case you still want to go the binary plugin route, don’t do it the (legacy) .dlx way. Create a Utilitiy Plugin ( *.dlu ) and use Function Publishing …
really depends on where and how you want to use the exposed functions, if in, say, a for loop called thousands of times then the “legacy” method has a nearly 3 times performance gain over function publishing. fp also has some short comings with regards object created within fp not been cleaned up with mxs garbage collector (though there are work arounds for this they are not pretty or elegant and beg the question why I didn’t use “legacy” anyway). I know dlx is a mess with some nasty quirks and evil #include file order issues, but for performance on often called functions there really is no alternative.
It seems to me that if one charges a fair amount for one’s script, then the motivation for cracking it is less…I’ve just finished writing around 20,000 lines of code, and I realize that I’m going to have to be realistic about what to charge. If it’s any good, autodesk may incorporate the system into their UI…who knows?
i think that no one can read 20,000 anyone else’s code, understand how it works, and be able use it for s/his own