source: postlfs/security/tripwire.xml@ 7f5c97e

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts krejzi/svn lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition systemd-11177 systemd-13485 trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 7f5c97e was 7f5c97e, checked in by Manuel Canales Esparcia <manuel@…>, 18 years ago

Made all dependencies an a mail server actual cross-references.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@6132 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 12.3 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!-- Inserted as a reminder to do this. The mention of a test suite
8 is usually right before the root user installation commands. Please
9 delete these 12 (including one blank) lines after you are done.-->
10
11 <!-- Use one of the two mentions below about a test suite,
12 delete the line that is not applicable. Of course, if the
13 test suite uses syntax other than "make check", revise the
14 line to reflect the actual syntax to run the test suite -->
15
16 <!-- <para>This package does not come with a test suite.</para> -->
17 <!-- <para>To test the results, issue: <command>make check</command>.</para> -->
18
19 <!ENTITY tripwire-download-http "http://prdownloads.sourceforge.net/tripwire/tripwire-&tripwire-version;-src.tar.bz2?download">
20 <!ENTITY tripwire-download-ftp " ">
21 <!ENTITY tripwire-md5sum "b371f79ac23cacc9ad40b1da76b4a0c4">
22 <!ENTITY tripwire-size "1.2 MB">
23 <!ENTITY tripwire-buildsize "37 MB">
24 <!ENTITY tripwire-time "1.6 SBU">
25]>
26
27<sect1 id="tripwire" xreflabel="Tripwire-&tripwire-version;">
28 <?dbhtml filename="tripwire.html"?>
29
30 <sect1info>
31 <othername>$LastChangedBy$</othername>
32 <date>$Date$</date>
33 <keywordset>
34 <keyword role="package">tripwire-&tripwire-version;.tar</keyword>
35 <keyword role="ftpdir">tripwire</keyword>
36 </keywordset>
37 </sect1info>
38
39 <title>Tripwire-&tripwire-version;</title>
40
41 <indexterm zone="tripwire">
42 <primary sortas="a-Tripwire">Tripwire</primary>
43 </indexterm>
44
45 <sect2 role="package">
46 <title>Introduction to Tripwire</title>
47
48 <para>The <application>Tripwire</application> package contains programs
49 used to verify the integrity of the files on a given system.</para>
50
51 <bridgehead renderas="sect3">Package Information</bridgehead>
52 <itemizedlist spacing="compact">
53 <listitem>
54 <para>Download (HTTP): <ulink url="&tripwire-download-http;"/></para>
55 </listitem>
56 <listitem>
57 <para>Download (FTP): <ulink url="&tripwire-download-ftp;"/></para>
58 </listitem>
59 <listitem>
60 <para>Download MD5 sum: &tripwire-md5sum;</para>
61 </listitem>
62 <listitem>
63 <para>Download size: &tripwire-size;</para>
64 </listitem>
65 <listitem>
66 <para>Estimated disk space required: &tripwire-buildsize;</para>
67 </listitem>
68 <listitem>
69 <para>Estimated build time: &tripwire-time;</para>
70 </listitem>
71 </itemizedlist>
72
73 <bridgehead renderas="sect3">Additional Downloads</bridgehead>
74 <itemizedlist spacing="compact">
75 <listitem>
76 <para>Required patch:
77 <ulink url="&patch-root;/tripwire-&tripwire-version;-gcc4_build_fixes-1.patch"/>
78 </para>
79 </listitem>
80 </itemizedlist>
81
82 <bridgehead renderas="sect3">Tripwire Dependencies</bridgehead>
83
84 <bridgehead renderas="sect4">Required</bridgehead>
85 <para role="required"><xref linkend="openssl"/></para>
86
87
88 <bridgehead renderas="sect4">Optional</bridgehead>
89 <para role="optional">An <xref linkend="server-mail"/></para>
90
91 <para condition="html" role="usernotes">User Notes:
92 <ulink url="&blfs-wiki;/tripwire"/></para>
93
94 </sect2>
95
96 <sect2 role="installation">
97 <title>Installation of Tripwire</title>
98
99 <para>Compile <application>Tripwire</application> by running the following
100 commands:</para>
101
102<screen><userinput>ln -s contrib install &amp;&amp;
103patch -Np1 -i ../tripwire-&tripwire-version;-gcc4_build_fixes-1.patch &amp;&amp;
104sed -i -e 's@TWDB="${prefix}@TWDB="/var@' install/install.cfg &amp;&amp;
105./configure --prefix=/usr --sysconfdir=/etc/tripwire &amp;&amp;
106make</userinput></screen>
107
108 <warning><para>The default configuration is to use a local MTA. If
109 you don't have an MTA installed and have no wish to install
110 one, modify <filename>install/install.cfg</filename> to use an SMTP
111 server instead. Otherwise the install will fail.</para></warning>
112
113 <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
114
115<screen role="root"><userinput>make install &amp;&amp;
116cp -v policy/*.txt /usr/share/doc/tripwire</userinput></screen>
117
118 </sect2>
119
120 <sect2 role="commands">
121 <title>Command Explanations</title>
122
123 <para><command>ln -s contrib install</command>: This command creates
124 a symbolic link in the build directory needed for installation.</para>
125
126 <para><command>sed -i -e 's@TWDB="${prefix}@TWDB="/var@'
127 install/install.cfg</command>: This command tells the package to install
128 the program database and reports in
129 <filename class="directory">/var/lib/tripwire</filename>.</para>
130
131 <para><command>make install</command>: This command creates the
132 <application>Tripwire</application> security keys as well as installing
133 the binaries. There are two keys: a site key and a local key which are
134 stored in <filename class="directory">/etc/tripwire/</filename>.</para>
135
136 <para><command>cp -v policy/*.txt /usr/share/doc/tripwire</command>: This
137 command installs the documentation.</para>
138
139 </sect2>
140
141 <sect2 role="configuration">
142 <title>Configuring Tripwire</title>
143
144 <sect3 id="tripwire-config">
145 <title>Config Files</title>
146
147 <para><filename>/etc/tripwire/*</filename></para>
148
149 <indexterm zone="tripwire tripwire-config">
150 <primary sortas="e-etc-tripwire">/etc/tripwire/*</primary>
151 </indexterm>
152
153 </sect3>
154
155 <sect3>
156 <title>Configuration Information</title>
157
158 <para><application>Tripwire</application> uses a policy file to
159 determine which files are integrity checked. The default policy
160 file (<filename>/etc/tripwire/twpol.txt</filename>) is for a
161 default Redhat installation and will need to be updated for your
162 system.</para>
163
164 <para>Policy files should be tailored to each individual distribution
165 and/or installation. Some custom policy files can be found below:</para>
166
167<literallayout><ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-all.txt"/>
168Checks integrity of all files
169<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-lfs.txt"/>
170Custom policy file for Base LFS 3.0 system
171<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-suse7.2.txt"/>
172Custom policy file for SuSE 7.2 system</literallayout>
173
174 <para>Download the custom policy file you'd like to try, copy it into
175 <filename class="directory">/etc/tripwire/</filename>, and use it instead
176 of <filename>twpol.txt</filename>. It is, however, recommended that you
177 make your own policy file. Get ideas from the examples above and read
178 <filename>/usr/share/doc/tripwire/policyguide.txt</filename> for
179 additional information. <filename>twpol.txt</filename> is a good policy
180 file for beginners as it will note any changes to the file system and can
181 even be used as an annoying way of keeping track of changes for
182 uninstallation of software.</para>
183
184 <para>After your policy file has been transferred to
185 <filename class="directory">/etc/tripwire/</filename> you may begin
186 the configuration steps (perform as the
187 <systemitem class='username'>root</systemitem>):</para>
188
189<screen role="root"><userinput>twadmin --create-polfile --site-keyfile /etc/tripwire/site.key \
190 /etc/tripwire/twpol.txt &amp;&amp;
191tripwire --init</userinput></screen>
192
193 </sect3>
194
195 <sect3>
196 <title>Usage Information</title>
197
198 <para>To use <application>Tripwire</application> after creating a policy
199 file to run a report, use the following command:</para>
200
201<screen role="root"><userinput>tripwire --check &gt; /etc/tripwire/report.txt</userinput></screen>
202
203 <para>View the output to check the integrity of your files. An automatic
204 integrity report can be produced by using a cron facility to schedule
205 the runs.</para>
206
207 <para>Please note that after you run an integrity check, you must
208 examine the report (or email) and then modify the
209 <application>Tripwire</application> database to reflect the changed
210 files on your system. This is so that <application>Tripwire</application>
211 will not continually notify you that files you intentionally changed are
212 a security violation. To do this you must first <command>ls -l
213 /var/lib/tripwire/report/</command> and note the name of the newest file
214 which starts with <filename>linux-</filename> and ends in
215 <filename>.twr</filename>. This encrypted file was created during the
216 last report creation and is needed to update the
217 <application>Tripwire</application> database of your system. Then, as the
218 <systemitem class='username'>root</systemitem> user, type
219 in the following command making the appropriate substitutions for
220 <replaceable>&lt;?&gt;</replaceable>:</para>
221
222<screen role="root"><userinput>tripwire --update -twrfile \
223 /var/lib/tripwire/report/linux-<replaceable>&lt;???????&gt;</replaceable>-<replaceable>&lt;??????&gt;</replaceable>.twr</userinput></screen>
224
225 <para>You will be placed into <application>vim</application> with a copy
226 of the report in front of you. If all the changes were good, then just
227 type <command>:x</command> and after entering your local key, the database
228 will be updated. If there are files which you still want to be warned
229 about, remove the 'x' before the filename in the report and type
230 <command>:x</command>.</para>
231
232
233 <para>A good summary of tripwire operations can be found at
234 <ulink url="http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/ch-tripwire.html"/>.</para>
235
236 </sect3>
237
238 <sect3>
239 <title>Changing the Policy File</title>
240
241 <para>If you are unhappy with your policy file and would like to modify
242 it or use a new one, modify the policy file and then execute the following
243 commands as the <systemitem class='username'>root</systemitem> user:</para>
244
245<screen role="root"><userinput>twadmin --create-polfile /etc/tripwire/twpol.txt &amp;&amp;
246tripwire --init</userinput></screen>
247
248 </sect3>
249
250 </sect2>
251
252 <sect2 role="content">
253 <title>Contents</title>
254
255 <segmentedlist>
256 <segtitle>Installed Programs</segtitle>
257 <segtitle>Installed Libraries</segtitle>
258 <segtitle>Installed Directories</segtitle>
259
260 <seglistitem>
261 <seg>siggen, tripwire, twadmin, and twprint.</seg>
262 <seg>None</seg>
263 <seg>/etc/tripwire, /usr/share/doc/tripwire, and /var/lib/tripwire</seg>
264 </seglistitem>
265 </segmentedlist>
266
267 <variablelist>
268 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
269 <?dbfo list-presentation="list"?>
270 <?dbhtml list-presentation="table"?>
271
272 <varlistentry id="siggen">
273 <term><command>siggen</command></term>
274 <listitem>
275 <para>is a signature gathering utility that displays
276 the hash function values for the specified files.</para>
277 <indexterm zone="tripwire siggen">
278 <primary sortas="b-siggen">siggen</primary>
279 </indexterm>
280 </listitem>
281 </varlistentry>
282
283 <varlistentry id='tripwire-program'>
284 <term><command>tripwire</command></term>
285 <listitem>
286 <para>is the main file integrity checking program.</para>
287 <indexterm zone="tripwire tripwire">
288 <primary sortas="b-tripwire">tripwire</primary>
289 </indexterm>
290 </listitem>
291 </varlistentry>
292
293 <varlistentry id='twadmin'>
294 <term><command>twadmin</command></term>
295 <listitem>
296 <para>administrative and utility tool used to perform
297 certain administrative functions related to
298 <application>Tripwire</application> files and configuration
299 options.</para>
300 <indexterm zone="tripwire twadmin">
301 <primary sortas="b-twadmin">twadmin</primary>
302 </indexterm>
303 </listitem>
304 </varlistentry>
305
306 <varlistentry id='twprint'>
307 <term><command>twprint</command></term>
308 <listitem>
309 <para>prints <application>Tripwire</application>
310 database and report files in clear text format.</para>
311 <indexterm zone="tripwire twprint">
312 <primary sortas="b-twprint">twprint</primary>
313 </indexterm>
314 </listitem>
315 </varlistentry>
316
317 </variablelist>
318
319 </sect2>
320
321</sect1>
Note: See TracBrowser for help on using the repository browser.