> So, how can you protect your mud from your own programmers?
>
> I was thinking about this problem for a while, and I realized that
> there was a sort of convuluted way to protect your code. See, if someone
> has access to your code, they can, no matter what you put in it,
> eventually download it, and run it as theirs. Sure, they may have to take
> out alot of platform/machine specific options, but eventually it will
> work. You can't simply just crypt your files either; if they're going to
> have to edit them....
>
Sounds a bit paranoid to me. One of circlemud's best features is
portability... say you loose your server and you need to port the mud people
have been adding junk to for several years... it's still easy to port the
whole thing, even with all the customizations.
The easiest solution is to (surprise) trust your coders. Not hiring
outside coders seems to help as well; instead, promote long-time players who
are loyal to the mud and have a working knowledge of C. They're not
terribly difficult to find.
--Ben Cartwright
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 04/10/01 PDT