Yes, there are.
There are two ways. The first is to password protect the code. This I
don't do for two reasons. The first is that one can buy password crackers
and the second is that I believe that the client owns the code.
The problem with protecting the code is that it can cheese off the client
somewhat. I was called in to a major firm because their templates were
broken and the person who wrote them password protected them and then went
off back backing around the other side of the world for six months.
After I had the password cracked she never worked for that client again.
If she didn't have the code password protected she would have continued
working for them when she returned.
So, basically, password protecting the code is, in my view, a waste of
time and counter-productive.
Now for really sensitive stuff; such as passwords, remote login-ids and
the like and for stuff which I really can't have open then I place the
code into an Active-X DLL and then through the COM interface I call that
code.
If you do it that way and have things like user-ids, passwords, URLs or
whatever which are sensitive then make sure that you don't just have them
in as a string; a hex editor can pick them out.
I usually construct sensitive strings from picking out letters from
phrases such as 'The Quick Brown Fox...' and so on.
At the end of the day, if you want to make your code secure; shove it into
a DLL otherwise it isn't as secure as you may think...
- Malc
www.dragondrop.com