
Then the author turned it into a program. At first it was just a set of instructions on how to use OllyDbg to bypass the password.

What if they were to open another instance of it? What if they were to log in and find how to bypass it and give the method to others (typical crack/hack methods) -> I may be quite off-base with this, but there's simple functions to detect debuggers and detach them immediately or invoke program shutdown (your program and/or the debugger) - Let me know a little more of the specifics and I'll try my best to help you out. What if the users were to try and debug something they're programming? ->If your answer is that once they've entered the password you can allow debugging. If that is the case, depending upon the language there are multiple ways to prevent any debugging of just your program while not stopping it from debugging other processes. Question: I may just be tired and slow right now, but as I understand it now, you've written a security program and they're attaching a debugger such as OllyDBG to your program which helps them to disable the password feature of your program.
