2004-06-10 13:47:11 +08:00
|
|
|
<?xml version="1.0" encoding="ISO-8859-1"?>
|
2005-04-04 04:52:42 +08:00
|
|
|
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
|
|
|
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
2004-06-10 13:47:11 +08:00
|
|
|
<!ENTITY % general-entities SYSTEM "../../general.ent">
|
|
|
|
%general-entities;
|
|
|
|
|
2006-04-27 18:48:30 +08:00
|
|
|
<!-- Inserted as a reminder to do this. The mention of a test suite
|
|
|
|
is usually right before the root user installation commands. Please
|
|
|
|
delete these 12 (including one blank) lines after you are done.-->
|
|
|
|
|
|
|
|
<!-- Use one of the two mentions below about a test suite,
|
|
|
|
delete the line that is not applicable. Of course, if the
|
|
|
|
test suite uses syntax other than "make check", revise the
|
|
|
|
line to reflect the actual syntax to run the test suite -->
|
|
|
|
|
|
|
|
<!-- <para>This package does not come with a test suite.</para> -->
|
|
|
|
<!-- <para>To test the results, issue: <command>make check</command>.</para> -->
|
|
|
|
|
2007-01-16 07:25:53 +08:00
|
|
|
<!ENTITY tripwire-download-http "http://downloads.sourceforge.net/tripwire/tripwire-&tripwire-version;-src.tar.bz2?download">
|
2004-12-22 11:48:05 +08:00
|
|
|
<!ENTITY tripwire-download-ftp " ">
|
2006-04-12 14:17:06 +08:00
|
|
|
<!ENTITY tripwire-md5sum "b371f79ac23cacc9ad40b1da76b4a0c4">
|
|
|
|
<!ENTITY tripwire-size "1.2 MB">
|
|
|
|
<!ENTITY tripwire-buildsize "37 MB">
|
|
|
|
<!ENTITY tripwire-time "1.6 SBU">
|
2004-06-10 13:47:11 +08:00
|
|
|
]>
|
|
|
|
|
2006-04-12 14:17:06 +08:00
|
|
|
<sect1 id="tripwire" xreflabel="Tripwire-&tripwire-version;">
|
2005-05-15 00:46:27 +08:00
|
|
|
<?dbhtml filename="tripwire.html"?>
|
|
|
|
|
|
|
|
<sect1info>
|
|
|
|
<othername>$LastChangedBy$</othername>
|
|
|
|
<date>$Date$</date>
|
|
|
|
</sect1info>
|
|
|
|
|
|
|
|
<title>Tripwire-&tripwire-version;</title>
|
|
|
|
|
2006-04-12 14:17:06 +08:00
|
|
|
<indexterm zone="tripwire">
|
2005-05-15 00:46:27 +08:00
|
|
|
<primary sortas="a-Tripwire">Tripwire</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
|
|
|
<sect2 role="package">
|
|
|
|
<title>Introduction to Tripwire</title>
|
|
|
|
|
|
|
|
<para>The <application>Tripwire</application> package contains programs
|
|
|
|
used to verify the integrity of the files on a given system.</para>
|
|
|
|
|
|
|
|
<bridgehead renderas="sect3">Package Information</bridgehead>
|
|
|
|
<itemizedlist spacing="compact">
|
|
|
|
<listitem>
|
|
|
|
<para>Download (HTTP): <ulink url="&tripwire-download-http;"/></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Download (FTP): <ulink url="&tripwire-download-ftp;"/></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Download MD5 sum: &tripwire-md5sum;</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Download size: &tripwire-size;</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Estimated disk space required: &tripwire-buildsize;</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Estimated build time: &tripwire-time;</para>
|
|
|
|
</listitem>
|
|
|
|
</itemizedlist>
|
|
|
|
|
2006-04-12 14:17:06 +08:00
|
|
|
<bridgehead renderas="sect3">Additional Downloads</bridgehead>
|
|
|
|
<itemizedlist spacing="compact">
|
|
|
|
<listitem>
|
|
|
|
<para>Required patch:
|
2006-04-13 00:05:51 +08:00
|
|
|
<ulink url="&patch-root;/tripwire-&tripwire-version;-gcc4_build_fixes-1.patch"/>
|
2006-04-12 14:17:06 +08:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</itemizedlist>
|
2006-05-27 01:50:22 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<bridgehead renderas="sect3">Tripwire Dependencies</bridgehead>
|
|
|
|
|
2006-04-13 13:23:05 +08:00
|
|
|
<bridgehead renderas="sect4">Required</bridgehead>
|
|
|
|
<para role="required"><xref linkend="openssl"/></para>
|
2006-05-27 01:50:22 +08:00
|
|
|
|
2006-04-13 13:23:05 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<bridgehead renderas="sect4">Optional</bridgehead>
|
2006-05-27 01:50:22 +08:00
|
|
|
<para role="optional">An <xref linkend="server-mail"/></para>
|
2005-05-15 00:46:27 +08:00
|
|
|
|
2006-04-11 02:38:22 +08:00
|
|
|
<para condition="html" role="usernotes">User Notes:
|
|
|
|
<ulink url="&blfs-wiki;/tripwire"/></para>
|
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 role="installation">
|
|
|
|
<title>Installation of Tripwire</title>
|
|
|
|
|
|
|
|
<para>Compile <application>Tripwire</application> by running the following
|
|
|
|
commands:</para>
|
|
|
|
|
2006-04-12 14:17:06 +08:00
|
|
|
<screen><userinput>ln -s contrib install &&
|
|
|
|
patch -Np1 -i ../tripwire-&tripwire-version;-gcc4_build_fixes-1.patch &&
|
|
|
|
sed -i -e 's@TWDB="${prefix}@TWDB="/var@' install/install.cfg &&
|
2004-12-22 11:48:05 +08:00
|
|
|
./configure --prefix=/usr --sysconfdir=/etc/tripwire &&
|
2005-05-15 00:46:27 +08:00
|
|
|
make</userinput></screen>
|
2005-01-27 11:26:52 +08:00
|
|
|
|
2006-04-12 14:17:06 +08:00
|
|
|
<warning><para>The default configuration is to use a local MTA. If
|
|
|
|
you don't have an MTA installed and have no wish to install
|
|
|
|
one, modify <filename>install/install.cfg</filename> to use an SMTP
|
|
|
|
server instead. Otherwise the install will fail.</para></warning>
|
2006-05-27 01:50:22 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<para>Now, as the <systemitem class="username">root</systemitem> user:</para>
|
2005-01-27 11:26:52 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<screen role="root"><userinput>make install &&
|
|
|
|
cp -v policy/*.txt /usr/share/doc/tripwire</userinput></screen>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
</sect2>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<sect2 role="commands">
|
|
|
|
<title>Command Explanations</title>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2006-05-27 01:50:22 +08:00
|
|
|
<para><command>ln -s contrib install</command>: This command creates
|
2006-04-12 14:17:06 +08:00
|
|
|
a symbolic link in the build directory needed for installation.</para>
|
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<para><command>sed -i -e 's@TWDB="${prefix}@TWDB="/var@'
|
|
|
|
install/install.cfg</command>: This command tells the package to install
|
|
|
|
the program database and reports in
|
|
|
|
<filename class="directory">/var/lib/tripwire</filename>.</para>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<para><command>make install</command>: This command creates the
|
|
|
|
<application>Tripwire</application> security keys as well as installing
|
|
|
|
the binaries. There are two keys: a site key and a local key which are
|
|
|
|
stored in <filename class="directory">/etc/tripwire/</filename>.</para>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<para><command>cp -v policy/*.txt /usr/share/doc/tripwire</command>: This
|
|
|
|
command installs the documentation.</para>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
</sect2>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<sect2 role="configuration">
|
|
|
|
<title>Configuring Tripwire</title>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<sect3 id="tripwire-config">
|
|
|
|
<title>Config Files</title>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<para><filename>/etc/tripwire/*</filename></para>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2006-04-12 14:17:06 +08:00
|
|
|
<indexterm zone="tripwire tripwire-config">
|
2005-05-15 00:46:27 +08:00
|
|
|
<primary sortas="e-etc-tripwire">/etc/tripwire/*</primary>
|
|
|
|
</indexterm>
|
2004-06-10 13:47:11 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
</sect3>
|
2004-07-01 11:36:22 +08:00
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
<sect3>
|
|
|
|
<title>Configuration Information</title>
|
|
|
|
|
|
|
|
<para><application>Tripwire</application> uses a policy file to
|
|
|
|
determine which files are integrity checked. The default policy
|
|
|
|
file (<filename>/etc/tripwire/twpol.txt</filename>) is for a
|
2005-07-27 03:55:34 +08:00
|
|
|
default Redhat installation and will need to be updated for your
|
2005-05-15 00:46:27 +08:00
|
|
|
system.</para>
|
|
|
|
|
|
|
|
<para>Policy files should be tailored to each individual distribution
|
|
|
|
and/or installation. Some custom policy files can be found below:</para>
|
|
|
|
|
|
|
|
<literallayout><ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-all.txt"/>
|
2004-06-10 13:47:11 +08:00
|
|
|
Checks integrity of all files
|
2004-07-01 11:36:22 +08:00
|
|
|
<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-lfs.txt"/>
|
2004-06-10 13:47:11 +08:00
|
|
|
Custom policy file for Base LFS 3.0 system
|
2004-07-01 11:36:22 +08:00
|
|
|
<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-suse7.2.txt"/>
|
2005-05-15 00:46:27 +08:00
|
|
|
Custom policy file for SuSE 7.2 system</literallayout>
|
|
|
|
|
|
|
|
<para>Download the custom policy file you'd like to try, copy it into
|
|
|
|
<filename class="directory">/etc/tripwire/</filename>, and use it instead
|
|
|
|
of <filename>twpol.txt</filename>. It is, however, recommended that you
|
|
|
|
make your own policy file. Get ideas from the examples above and read
|
|
|
|
<filename>/usr/share/doc/tripwire/policyguide.txt</filename> for
|
|
|
|
additional information. <filename>twpol.txt</filename> is a good policy
|
|
|
|
file for beginners as it will note any changes to the file system and can
|
|
|
|
even be used as an annoying way of keeping track of changes for
|
|
|
|
uninstallation of software.</para>
|
|
|
|
|
|
|
|
<para>After your policy file has been transferred to
|
|
|
|
<filename class="directory">/etc/tripwire/</filename> you may begin
|
2005-07-27 03:55:34 +08:00
|
|
|
the configuration steps (perform as the
|
|
|
|
<systemitem class='username'>root</systemitem>):</para>
|
2005-05-15 00:46:27 +08:00
|
|
|
|
|
|
|
<screen role="root"><userinput>twadmin --create-polfile --site-keyfile /etc/tripwire/site.key \
|
2005-01-13 09:25:45 +08:00
|
|
|
/etc/tripwire/twpol.txt &&
|
2005-05-15 00:46:27 +08:00
|
|
|
tripwire --init</userinput></screen>
|
|
|
|
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3>
|
|
|
|
<title>Usage Information</title>
|
|
|
|
|
|
|
|
<para>To use <application>Tripwire</application> after creating a policy
|
|
|
|
file to run a report, use the following command:</para>
|
|
|
|
|
|
|
|
<screen role="root"><userinput>tripwire --check > /etc/tripwire/report.txt</userinput></screen>
|
|
|
|
|
|
|
|
<para>View the output to check the integrity of your files. An automatic
|
|
|
|
integrity report can be produced by using a cron facility to schedule
|
|
|
|
the runs.</para>
|
|
|
|
|
|
|
|
<para>Please note that after you run an integrity check, you must
|
|
|
|
examine the report (or email) and then modify the
|
|
|
|
<application>Tripwire</application> database to reflect the changed
|
|
|
|
files on your system. This is so that <application>Tripwire</application>
|
|
|
|
will not continually notify you that files you intentionally changed are
|
|
|
|
a security violation. To do this you must first <command>ls -l
|
|
|
|
/var/lib/tripwire/report/</command> and note the name of the newest file
|
|
|
|
which starts with <filename>linux-</filename> and ends in
|
|
|
|
<filename>.twr</filename>. This encrypted file was created during the
|
|
|
|
last report creation and is needed to update the
|
2005-07-27 03:55:34 +08:00
|
|
|
<application>Tripwire</application> database of your system. Then, as the
|
|
|
|
<systemitem class='username'>root</systemitem> user, type
|
2005-05-15 00:46:27 +08:00
|
|
|
in the following command making the appropriate substitutions for
|
2006-04-11 02:38:22 +08:00
|
|
|
<replaceable><?></replaceable>:</para>
|
2005-05-15 00:46:27 +08:00
|
|
|
|
|
|
|
<screen role="root"><userinput>tripwire --update -twrfile \
|
2006-04-11 02:38:22 +08:00
|
|
|
/var/lib/tripwire/report/linux-<replaceable><???????></replaceable>-<replaceable><??????></replaceable>.twr</userinput></screen>
|
2005-05-15 00:46:27 +08:00
|
|
|
|
|
|
|
<para>You will be placed into <application>vim</application> with a copy
|
|
|
|
of the report in front of you. If all the changes were good, then just
|
|
|
|
type <command>:x</command> and after entering your local key, the database
|
|
|
|
will be updated. If there are files which you still want to be warned
|
|
|
|
about, remove the 'x' before the filename in the report and type
|
|
|
|
<command>:x</command>.</para>
|
|
|
|
|
2006-05-27 01:50:22 +08:00
|
|
|
|
|
|
|
<para>A good summary of tripwire operations can be found at
|
2006-04-12 14:17:06 +08:00
|
|
|
<ulink url="http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/ch-tripwire.html"/>.</para>
|
|
|
|
|
2005-05-15 00:46:27 +08:00
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3>
|
|
|
|
<title>Changing the Policy File</title>
|
|
|
|
|
|
|
|
<para>If you are unhappy with your policy file and would like to modify
|
|
|
|
it or use a new one, modify the policy file and then execute the following
|
2005-07-27 03:55:34 +08:00
|
|
|
commands as the <systemitem class='username'>root</systemitem> user:</para>
|
2005-05-15 00:46:27 +08:00
|
|
|
|
|
|
|
<screen role="root"><userinput>twadmin --create-polfile /etc/tripwire/twpol.txt &&
|
|
|
|
tripwire --init</userinput></screen>
|
|
|
|
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 role="content">
|
|
|
|
<title>Contents</title>
|
|
|
|
|
|
|
|
<segmentedlist>
|
|
|
|
<segtitle>Installed Programs</segtitle>
|
|
|
|
<segtitle>Installed Libraries</segtitle>
|
|
|
|
<segtitle>Installed Directories</segtitle>
|
|
|
|
|
|
|
|
<seglistitem>
|
|
|
|
<seg>siggen, tripwire, twadmin, and twprint.</seg>
|
|
|
|
<seg>None</seg>
|
|
|
|
<seg>/etc/tripwire, /usr/share/doc/tripwire, and /var/lib/tripwire</seg>
|
|
|
|
</seglistitem>
|
|
|
|
</segmentedlist>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
|
|
|
<?dbfo list-presentation="list"?>
|
|
|
|
<?dbhtml list-presentation="table"?>
|
|
|
|
|
|
|
|
<varlistentry id="siggen">
|
|
|
|
<term><command>siggen</command></term>
|
|
|
|
<listitem>
|
|
|
|
<para>is a signature gathering utility that displays
|
|
|
|
the hash function values for the specified files.</para>
|
2006-04-12 14:17:06 +08:00
|
|
|
<indexterm zone="tripwire siggen">
|
2005-05-15 00:46:27 +08:00
|
|
|
<primary sortas="b-siggen">siggen</primary>
|
|
|
|
</indexterm>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2006-04-12 14:17:06 +08:00
|
|
|
<varlistentry id='tripwire-program'>
|
2005-05-15 00:46:27 +08:00
|
|
|
<term><command>tripwire</command></term>
|
|
|
|
<listitem>
|
|
|
|
<para>is the main file integrity checking program.</para>
|
2006-04-12 14:17:06 +08:00
|
|
|
<indexterm zone="tripwire tripwire">
|
2005-05-15 00:46:27 +08:00
|
|
|
<primary sortas="b-tripwire">tripwire</primary>
|
|
|
|
</indexterm>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry id='twadmin'>
|
|
|
|
<term><command>twadmin</command></term>
|
|
|
|
<listitem>
|
|
|
|
<para>administrative and utility tool used to perform
|
|
|
|
certain administrative functions related to
|
|
|
|
<application>Tripwire</application> files and configuration
|
|
|
|
options.</para>
|
2006-04-12 14:17:06 +08:00
|
|
|
<indexterm zone="tripwire twadmin">
|
2005-05-15 00:46:27 +08:00
|
|
|
<primary sortas="b-twadmin">twadmin</primary>
|
|
|
|
</indexterm>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry id='twprint'>
|
|
|
|
<term><command>twprint</command></term>
|
|
|
|
<listitem>
|
|
|
|
<para>prints <application>Tripwire</application>
|
|
|
|
database and report files in clear text format.</para>
|
2006-04-12 14:17:06 +08:00
|
|
|
<indexterm zone="tripwire twprint">
|
2005-05-15 00:46:27 +08:00
|
|
|
<primary sortas="b-twprint">twprint</primary>
|
|
|
|
</indexterm>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
</variablelist>
|
|
|
|
|
|
|
|
</sect2>
|
2004-07-01 11:36:22 +08:00
|
|
|
|
2002-07-08 04:28:42 +08:00
|
|
|
</sect1>
|