| /freebsd/sys/security/mac/ |
| H A D | mac_system.c | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| H A D | mac_pipe.c | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| H A D | mac_process.c | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| H A D | mac_vfs.c | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| H A D | mac_internal.h | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| H A D | mac_net.c | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| H A D | mac_syscalls.c | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| H A D | mac_framework.c | 9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
9aeffb2b Sat Oct 19 20:30:12 GMT 2002 Robert Watson <rwatson@FreeBSD.org> Make sure to clear the 'registered' flag for MAC policies when they
unregister. Under some obscure (perhaps demented) circumstances,
this can result in a panic if a policy is unregistered, and then someone
foolishly unregisters it again.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|