|
|
I hate to say it but I think this might be better on a security daemon that's connected to the server through RCON rather than on Skulltag itself. An example of what I mean is like with ircd. You can choose whatever daemon you want, and whatever security program you want, and whatever services daemon you want. This way, you can get all your favorite features of your favorite ircd, along with the security and peace of mind of the security daemon you choose. An ircd never forces a security process on you internally, and it is quite rare that an ircd should have one built in.
Of course, I was only using ircd as an example but I think it makes a strong case. I think if a security program such as the one you proposed is developed, it should be kept outside the Skulltag executable, and possibly even open source. |
|