Security mechanisms

Large systems have vulnerable spots, and MUSHes/MUXes are no exception. To prevent some of the more obvious vulnerabilities, there are many security-related mechanisms, often unrelated. Security processes can fail in two ways: failure to recognize a problem, or recognition of a problem when there is none. Because of the simple nature of the security mechanisms within MUSH, it is often that a limit of some sort is inconveniently reached.

There are several general security mechanisms within MUX:

• OOC Money system
• Command queue limit
• Function invocation limit
• Recursion limit
• Parent depth limit
• Object quota
• Site access controls
• CPU time limit (PennMUSH, RhostMUSH, TinyMUX)

Softcode-oriented and customizable solutions:

• Attribute controls
• Locks

Here's a list of some related commands and options:

Limit configuration options:

output_limit, function_invocation_limit, trace_output_limit, player_queue_limit, stack_limit, notify_recursion_limit, lock_recursion_limit, lag_limit, retry_limit, parent_recursion_limit, function_recursion_limit, earn_limit, zone_recursion_limit

Site restriction options:

suspect_site, permit_site, guest_site, trust_site, badsite_file, register_site, nositemon_site, forbid_site

... This needs to be expanded. A lot.