Stub protection technique?
As many DirectL regulars know, I’m in the planning stage of revamping my freely distributed generic stub package. The idea is to generate a stub from a mui-gui rather than use an editable lingo.ini, and allow a choice of desktop environment xtras.
A larger issue that I want to deal with first, though, is misuse of published stubs. If you’re one of the professionals that have shelled out the coins for whatever xtras might be used in a stub, then you know how a stub might be reused by others without purchasing a license for the xtras used therein. I’m not elaborating for obvious reasons :)
What I want to do is include a mechanism in a generated stub so that it will halt if not used with an intended project.. With some xtras for the desktop environment, any temporary settings are reset automatically when the application terminates, yet with others such needs to be accomplished explicitly in a return to the stub. Either way the mechanism needs to be in the stub (the stub being reused, not the presentation, is the issue here). I also understand that no mechanism is perfect - it just needs to be difficult to get around.
One preliminary thought I had was to embed a user specified key in the published stub that the author would set a global to in the actual project. I’m at a loss though in how the stub would subsequently check such without having to actually return to the stub from the project, and having a timer in the stub to check that the verification was accomplished. All the simpler ideas I know how to implement, I have rejected because they are too easy to get around.
So, without running on, I would appreciate any ideas/techniques/whatever in this matter.
Thank you,
Lee C
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
