6887492c26
While it's true that it's part of the traditional 4.4BSD security model, there may come a time where a different "primary" security model used for fine-grained privileges (ie., splitting root's responsibilities to various privileges that can be assigned) may want to still have a securelevel setting. Idea from Daniel Carosone: http://mail-index.netbsd.org/tech-security/2006/08/25/0001.html The location of the removed files, for reference, was: src/secmodel/bsd44/secmodel_bsd44_securelevel.c src/secmodel/bsd44/securelevel.h
17 lines
336 B
Plaintext
17 lines
336 B
Plaintext
# $NetBSD: files.secmodel,v 1.2 2007/11/21 22:49:07 elad Exp $
|
|
|
|
#
|
|
# Traditional 4.4BSD - Securelevel
|
|
#
|
|
include "secmodel/securelevel/files.securelevel"
|
|
|
|
#
|
|
# Traditional NetBSD (derived from 4.4BSD)
|
|
#
|
|
include "secmodel/bsd44/files.bsd44"
|
|
|
|
#
|
|
# Sample overlay model on-top of the traditional one
|
|
#
|
|
include "secmodel/overlay/files.overlay"
|