| /freebsd/sys/modules/mac_seeotheruids/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/mac_biba/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/mac_test/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/mac_ifoff/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/mac_none/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/mac_mls/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/mac_bsdextended/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/mac_stub/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| /freebsd/sys/modules/ |
| H A D | Makefile | diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
diff ebbd4fa8c8427d3dd847ba33c45c996e0500e6ff Thu Aug 01 19:41:27 CEST 2002 Robert Watson <rwatson@FreeBSD.org> Introduce support for Mandatory Access Control and extensible
kernel access control.
Hook up various policy modules to the kernel build.
Note that a number of these modules require futher entry point commits
in the remainder of the kernel to become fully functional, but enough
of the pieces are in place to allow experimentation.
Note also that it would be desirable to not build the mac_*.ko modules
if 'options MAC' is not defined in the kernel configuration, because
the resulting modules are not useful without the kernel option. There
doesn't appear to be precedent for a way to do this -- for example,
we allow ipfw.ko to be built even if 'options NETINET' isn't defined.
Suggests welcomed on the "best" way to do this.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|