source: postlfs/security/tripwire.xml@ 8abd5653

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 6.0 6.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 8abd5653 was e40cb61, checked in by Randy McMurchy <randy@…>, 20 years ago

Minor clean-up to GnuPG and Tripwire

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

  • Property mode set to 100644
File size: 8.5 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
3 "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY tripwire-download-http "http://prdownloads.sourceforge.net/tripwire/tripwire-&tripwire-version;.tar.gz">
8 <!ENTITY tripwire-download-ftp "ftp://ftp.fu-berlin.de/unix/security/tripwire/tripwire-&tripwire-version;.tar.gz">
9 <!ENTITY tripwire-size "1.4 MB">
10 <!ENTITY tripwire-buildsize "63 MB">
11 <!ENTITY tripwire-time "2.35 SBU">
12]>
13
14<sect1 id="tripwire" xreflabel="Tripwire-&tripwire-version;">
15<?dbhtml filename="tripwire.html"?>
16<title>Tripwire-&tripwire-version;</title>
17
18<sect2>
19<title>Introduction to <application>Tripwire</application></title>
20
21<para>The <application>Tripwire</application> package contains programs used
22to verify the integrity of the files on a given system.</para>
23
24<sect3><title>Package information</title>
25<itemizedlist spacing='compact'>
26<listitem><para>Download (HTTP): <ulink
27url="&tripwire-download-http;"/></para></listitem>
28<listitem><para>Download (FTP): <ulink
29url="&tripwire-download-ftp;"/></para></listitem>
30<listitem><para>Download size: &tripwire-size;</para></listitem>
31<listitem><para>Estimated Disk space required:
32&tripwire-buildsize;</para></listitem>
33<listitem><para>Estimated build time:
34&tripwire-time;</para></listitem></itemizedlist>
35</sect3>
36
37<sect3><title>Additional downloads</title>
38<itemizedlist spacing='compact'>
39<listitem><para>Required patch to fix multiple build issues (see patch for
40more information): <ulink
41url="&patch-root;/tripwire-&tripwire-version;-gcc3_build_fixes-1.patch"/></para></listitem>
42</itemizedlist>
43</sect3>
44
45<sect3><title><application>Tripwire</application> dependencies</title>
46<sect4><title>Optional</title>
47<para><acronym>MTA</acronym> (See <xref linkend="server-mail"/>)</para></sect4>
48</sect3>
49
50</sect2>
51
52<sect2>
53<title>Installation of <application>Tripwire</application></title>
54
55<para>Compile <application>Tripwire</application> by running the following
56commands:</para>
57
58<screen><userinput><command>patch -Np1 -i ../tripwire-&tripwire-version;-gcc3_build_fixes-1.patch &amp;&amp;
59make -C src release &amp;&amp;
60cp install/install.{sh,cfg} .</command></userinput></screen>
61
62<para>The default configuration is to use a local <acronym>MTA</acronym>. If
63you don't have an <acronym>MTA</acronym> installed and have no wish to install
64one, modify <filename>install.cfg</filename> to use an <acronym>SMTP</acronym>
65server instead. Install <application>Tripwire</application> by running the
66following commands:</para>
67
68<screen><userinput><command>./install.sh &amp;&amp;
69cp /etc/tripwire/tw.cfg /usr/sbin &amp;&amp;
70cp policy/*.txt /usr/share/doc/tripwire</command></userinput></screen>
71
72</sect2>
73
74<sect2>
75<title>Command explanations</title>
76
77<para><command>make release</command>: This command creates the
78<application>Tripwire</application> binaries.</para>
79
80<para><command>cp install.{sh,cfg} .</command>: These files are copied to
81the main <application>Tripwire</application> directory so that the script
82can be used to install the package.</para>
83
84<para><command>cp policy/*.txt /usr/share/doc/tripwire</command>: This command
85installs the documentation.</para>
86
87</sect2>
88
89<sect2>
90<title>Configuring <application>Tripwire</application></title>
91
92<sect3><title>Config files</title>
93<para><filename>/etc/tripwire/*</filename></para>
94</sect3>
95
96<sect3><title>Configuration Information</title>
97
98<para><application>Tripwire</application> uses a policy file to determine which
99files are integrity checked. The default policy file
100(<filename>/etc/tripwire/twpol.txt</filename>) is for a default
101installation of Redhat 7.0 and is woefully outdated.</para>
102
103<para>Policy files are also a custom thing and should be tailored to each
104individual distribution and/or installation. Some custom policy files can be
105found below: </para>
106
107<screen><ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-all.txt"/>
108Checks integrity of all files
109<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-lfs.txt"/>
110Custom policy file for Base LFS 3.0 system
111<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-suse7.2.txt"/>
112Custom policy file for SuSE 7.2 system</screen>
113
114<para>Download the custom policy file you'd like to try, copy it into
115<filename class="directory">/etc/tripwire/</filename>, and use it instead of
116<filename>twpol.txt</filename>. It is, however, recommended that you make
117your own policy file. Get ideas from the examples above and read
118<filename>/usr/share/doc/tripwire/policyguide.txt</filename> for additional
119information. <filename>twpol.txt</filename> is a good policy file for beginners
120as it will note any changes to the file system and can even be used as an
121annoying way of keeping track of changes for uninstallation of software.</para>
122
123<para>After your policy file has been transferred to
124<filename class="directory">/etc/tripwire/</filename> you may begin the
125configuration steps:</para>
126
127<screen><userinput><command>twadmin -m P /etc/tripwire/twpol.txt &amp;&amp;
128tripwire -m i</command></userinput></screen>
129
130<para>During installation <application>Tripwire</application> will create two
131keys: a site key and a local key which are stored in
132<filename class="directory">/etc/tripwire/</filename>.</para>
133
134</sect3>
135
136<sect3><title>Usage Information</title>
137<para>To use <application>Tripwire</application> after creating a policy file
138to run a report, use the following command:</para>
139
140<screen><userinput><command>tripwire -m c &gt; /etc/tripwire/report.txt</command></userinput></screen>
141
142<para>View the output to check the integrity of your files. An automatic
143integrity report can be produced by using a cron facility to schedule
144the runs.</para>
145
146<para>Please note that after you run an integrity check, you must examine
147the report (or email) and then modify the <application>Tripwire</application>
148database to reflect the changed files on your system. This is so that
149<application>Tripwire</application> will not continually notify you that
150files you intentionally changed are a security violation. To do this you
151must first <command>ls -l /var/lib/tripwire/report/</command> and note
152the name of the newest file which starts with <filename>linux-</filename> and
153ends in <filename>.twr</filename>. This encrypted file was created during the
154last report creation and is needed to update the
155<application>Tripwire</application> database of your
156system. Then, type in the following command making the appropriate
157substitutions for <replaceable>[?]</replaceable>:</para>
158
159<screen><userinput><command>tripwire -m u -r /var/lib/tripwire/report/linux-<replaceable>[???????]</replaceable>-<replaceable>[??????]</replaceable>.twr</command></userinput></screen>
160
161<para>You will be placed into <application>vim</application> with a copy of
162the report in front of you. If all the changes were good, then just type
163<command>:x</command> and after entering your local key, the database will be
164updated. If there are files which you still want to be warned about, remove the
165'x' before the filename in the report and type <command>:x</command>.</para>
166
167</sect3>
168
169<sect3><title>Changing the Policy File</title>
170
171<para>If you are unhappy with your policy file and would like to modify it or
172use a new one, modify the policy file and then execute the following
173commands:</para>
174
175<screen><userinput><command>twadmin -m P /etc/tripwire/twpol.txt &amp;&amp;
176tripwire -m i</command></userinput></screen>
177
178</sect3>
179
180</sect2>
181
182<sect2>
183<title>Contents</title>
184
185<para>The <application>Tripwire</application> package contains
186<command>siggen</command>, <command>tripwire</command>,
187<command>twadmin</command> and <command>twprint</command>.</para>
188
189</sect2>
190
191<sect2>
192<title>Description</title>
193
194<sect3>
195<title>siggen</title>
196<para><command>siggen</command> is a signature gathering utility that displays
197the hash function values for the specified files.</para></sect3>
198
199<sect3>
200<title>tripwire</title>
201<para><command>tripwire</command> is the main file integrity checking program.
202</para></sect3>
203
204<sect3>
205<title>twadmin</title>
206<para><command>twadmin</command> is <application>Tripwire</application>'s
207administrative and utility tool used to perform certain administrative
208functions related to <application>Tripwire</application> files and
209configuration options.</para></sect3>
210
211<sect3>
212<title>twprint</title>
213<para><command>twprint</command> prints <application>Tripwire</application>
214database and report files in clear text format.</para></sect3>
215
216</sect2>
217
218</sect1>
219
Note: See TracBrowser for help on using the repository browser.