freebsd-nq/sys/security/mac
Robert Watson a13c67da35 If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the
compile fail.  MAC_MAX_POLICIES should always be defined, or we have
bigger problems at hand.

Obtained from:	TrustedBSD Project
Sponsored by:	DARPA, Network Associates Laboratories
2002-10-20 03:41:09 +00:00
..
mac_framework.c If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00
mac_framework.h Integrate mac_check_socket_send() and mac_check_socket_receive() 2002-10-06 14:39:15 +00:00
mac_internal.h If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00
mac_net.c If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00
mac_pipe.c If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00
mac_policy.h Integrate mac_check_socket_send() and mac_check_socket_receive() 2002-10-06 14:39:15 +00:00
mac_process.c If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00
mac_syscalls.c If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00
mac_system.c If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00
mac_vfs.c If MAC_MAX_POLICIES isn't defined, don't try to define it, just let the 2002-10-20 03:41:09 +00:00