The securelevel does not affect whether Veriexec's tables can be modified;
this is now controlled by Veriexec's strict level.
This commit is contained in:
parent
7230395132
commit
03e754fd4d
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: init.8,v 1.36 2005/07/01 17:07:33 wiz Exp $
|
||||
.\" $NetBSD: init.8,v 1.37 2005/11/13 18:39:53 elad Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1991, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
|
@ -32,7 +32,7 @@
|
|||
.\"
|
||||
.\" @(#)init.8 8.6 (Berkeley) 5/26/95
|
||||
.\"
|
||||
.Dd June 30, 2005
|
||||
.Dd November 13, 2005
|
||||
.Dt INIT 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -174,10 +174,6 @@ be turned off; disks for mounted filesystems,
|
|||
and
|
||||
.Pa /dev/kmem
|
||||
are read-only.
|
||||
.Pp
|
||||
The verified exec in-kernel fingerprint table may not be changed
|
||||
(see
|
||||
.Xr veriexecctl 8 ) .
|
||||
.It Ic 2
|
||||
Highly secure mode \- same as secure mode, plus disks are always
|
||||
read-only whether mounted or not, new disks may not be mounted,
|
||||
|
|
Loading…
Reference in New Issue