NetBSD/sys/secmodel/bsd44/files.bsd44
elad 6887492c26 Make securelevel a "secmodel" of its own.
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
2007-11-21 22:49:05 +00:00

9 lines
343 B
Plaintext

# $NetBSD: files.bsd44,v 1.2 2007/11/21 22:49:07 elad Exp $
defflag secmodel_bsd44_logic
defflag secmodel_bsd44 : secmodel_bsd44_logic, secmodel_securelevel
file secmodel/bsd44/secmodel_bsd44.c secmodel_bsd44
file secmodel/bsd44/secmodel_bsd44_logic.c secmodel_bsd44_logic
file secmodel/bsd44/secmodel_bsd44_suser.c secmodel_bsd44_logic