1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
@c -*-texinfo-*-
@c This is part of the Integrit File Verification System Manual.
@c Copyright (C) 2000, 2001 Ed L. Cashin
@c See the file integrit.texi for copying conditions.
@setfilename ../info/faq
@c Copyright (C) 2000, 2001 Ed L. Cashin
@c
@c This program is free software; you can redistribute it and/or
@c modify it under the terms of the GNU General Public License
@c as published by the Free Software Foundation; either version 2
@c of the License, or (at your option) any later version.
@c
@c This program is distributed in the hope that it will be useful,
@c but WITHOUT ANY WARRANTY; without even the implied warranty of
@c MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
@c GNU General Public License for more details.
@c
@c You should have received a copy of the GNU General Public License
@c along with this program; if not, write to the Free Software
@c Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
@c
@comment node-name, next, previous, up
@node FAQ, Resources, Auxiliary Tools, Top
@chapter FAQ
@cindex FAQ
@menu
* Win32:: What about Win32 support?
* Regular Expressions:: What about regular expressions in the conf file?
* Trailing Slash:: Why doesn't "! /proc/" work?
@c * MD5 Sum Changes:: The MD5 sum is different everytime I do an update!
@c * Failing opendir:: Why doesn't integrit keep running when it can't open a directory?
@end menu
@node Win32
@section Win32
@cindex Windows
Q: What about Win32 support?
A few people have asked about Win32 support. In short, go for it.
I'm not interested in using Win32, but by using Cygwin, djgpp, and
or some other POSIX/UNIX emulation platform, you could probably have
some success.
Please let us know if you do this. (integrit-users at lists.sf.net)
@node Regular Expressions
@section Regular Expressions
@cindex Regular Expressions
Q: What about regular expressions in the conf file?
It usually occurs to an integrit user at some point, "Wouldn't it be
nice to use regular expressions in the integrit configuration file
instead of literal paths?" The answer is that, yes, that would be
convenient, but it isn't likely to happen.
The added runtime cost of compiling regular expression objects and
evaluating all the pathnames would be substantial, and it would make
integrit more complex. Better to leave integrit stable and simple and
then list files explicitly in the configuration file.
After all, you have all kinds of unix tools (find, grep, etc.), that can
help you create the configuration file using regular expressions!
@c @node Failing opendir
@c @section Failing opendir
@c @cindex Failing opendir
@c
@node Trailing Slash
@section Trailing Slash
@cindex Trailing Slash
Q: Why does integrit scan /proc when I put "! /proc/" in the
configuration file?
Trailing slashes aren't part of a directory's name. Leave them out in
the configuration file.
For example, to ignore @code{/var/tmp}, this will work:
@example
! /tmp
@end example
... but this will not:
@example
# WRONG: trailing slash
! /tmp/
@end example
@c @node MD5 Sum Changes
@c @section MD5 Sum Changes
@c @cindex MD5 Sum Changes
@c
@c Q: Why does the MD5 sum change everytime I do an update?
@c
@c To be specific, the MD5 sum is a checksum of the @emph{current} (or new)
@c database. It will be different everytime you tell integrit to update
@c the current database with the @code{-u} option. Here's why @dots{}
@c
@c For each file integrit visits, there's a record in the current database,
@c and part of each record is a file stat structure. You can see what's in
@c that structure by reading your system's @code{stat(2)} manpage.
@c
@c The file stat structure contains both the file's access time and the
@c "change time". The change time is updated whenever the information
@c associated with the inode is changed. For example, if you tell integrit
@c to reset the file's access time after integrit reads the contents of the
@c file to do a checksum, then that means that the change time for the file
@c will change
|
