1 .\" $NetBSD: veriexecctl.8,v 1.33 2008/02/15 15:33:56 elad Exp $
4 .\" Brett Lymn - blymn@baea.com.au, brett_lymn@yahoo.com.au
6 .\" This code is donated to The NetBSD Foundation by the author.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. The name of the Author may not be used to endorse or promote
17 .\" products derived from this software without specific prior written
20 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" $Id: veriexec.5,v 1.1 2008/02/18 10:37:19 elad Exp $
44 loads entries to the in-kernel database from a file describing files to be
45 monitored and the type of monitoring.
46 This file is often referred to as the
47 .Sq signatures database
51 The signatures file can be easily created using
53 .Sh SIGNATURES DATABASE FORMAT
54 The signatures database has a line based structure, where each line has several
55 fields separated by white-space (space, tabs, etc.) taking the following form:
57 .Dl path type fingerprint flags
59 The description for each field is as follows:
62 The full path to the file.
63 White-space characters can be escaped if prefixed with a
66 Type of fingerprinting algorithm used for the file.
68 Requires kernel support for the specified algorithm.
69 List of fingerprinting algorithms supported by the kernel can be obtained by
70 using the following command:
71 .Bd -literal -offset indent
72 # sysctl kern.veriexec.algorithms
75 The fingerprint for the file.
76 Can (usually) be generated using the following command:
77 .Bd -literal -offset indent
78 % cksum -a \*[Lt]algorithm\*[Gt] \*[Lt]file\*[Gt]
81 Optional listing of entry flags, separated by a comma.
85 Allow direct execution only.
87 Execution of a program is said to be
89 when the program is invoked by the user (either in a script, manually typing it,
94 Allow indirect execution only.
96 Execution of a program is said to be
98 if it is invoked by the kernel to interpret a script
101 Allow opening the file only, via the
103 syscall (no execution is allowed).
105 Indicate that the file is located on untrusted storage and its fingerprint
106 evaluation status should not be cached, but rather re-calculated each time
108 .\"It also enabled per-page fingerprints for the file, causing pages it as
109 .\"backing store to be verified for their integrity as well.
111 Fingerprints for untrusted files will always be evaluated on load.
114 To improve readaibility of the signatures file, the following aliases are
135 If no flags are specified,
140 Comments begin with a
142 character and span to the end of the line.
154 .An Brett Lymn Aq blymn@NetBSD.org
155 .An Elad Efrat Aq elad@NetBSD.org