source: postlfs/security/tripwire/tripwire-config.xml@ c62afe4

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 v1_0 v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since c62afe4 was c62afe4, checked in by Larry Lawrence <larry@…>, 21 years ago

really add tripwire

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

  • Property mode set to 100644
File size: 3.7 KB
Line 
1<sect2>
2<title>Configuring tripwire</title>
3
4<sect3><title>Config files</title>
5<para><userinput>/etc/tripwire</userinput></para>
6</sect3>
7
8<sect3><title>Configuration Information</title>
9
10<para>Tripwire uses a policy file to determine which files integrity
11 are checked. The default policy file (<filename>twpol.txt</filename> found in
12<filename>/etc/tripwire/</filename>) is for a default installation of Redhat
137.0 and is woefully outdated.</para>
14
15<para>Policy files are also a custom thing and should be tailored to
16 each individual distro and/or installation. Some custom policy files
17 can be found below: </para>
18 <screen> <ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-all.txt"/>
19Checks integrity of all files
20<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-lfs.txt"/>
21Custom policy file for Base LFS 3.0 system
22<ulink url="http://home.iprimus.com.au/glombowski/blfs/twpol-suse7.2.txt"/>
23Custom policy file for SuSE 7.2 system
24</screen>
25
26 <para>Download the custom policy file you'd like to try, copy it into
27 /etc/tripwire/, and use it instead of <filename>twpol.txt</filename>. It
28 is, however, recommended that you make your own policy file. Get ideas
29 from the examples above and read
30 <filename>/usr/share/doc/tripwire/policyguide.txt</filename>.
31<filename>twpol.txt</filename> is a good policy file for beginners as it will note any changes to the filesystem and can even be used as an annoying way of keeping track of changes for uninstallation of software.</para>
32
33 <para>After your policy file has been transferred to <filename>/etc/tripwire/</filename> you may begin the configuation steps:</para>
34
35<screen><userinput>twadmin -m P /etc/tripwire/twpol.txt &amp;&amp;
36tripwire -m i</userinput></screen>
37
38<para>During configuration tripwire will create 2 keys: a site key and
39 a local key which will be stored in /etc/tripwire/.</para>
40
41</sect3>
42
43<sect3><title>Usage Information</title>
44<para>To use tripwire after this and run a report using the following command:
45
46<screen><userinput>tripwire -m c &gt; /etc/tripwire/report.txt</userinput></screen>
47
48<para>View the output to check the integrity of your files. An automatic
49integrity report can be produced by using fcron. </para>
50
51<para>Please note that after you run an integrity check, you must check
52the report or email and then modify the tripwire database of the files
53on your system so that tripwire will not continually notify you that
54files you intentionally changed are a security violation. To do this you
55must first <userinput>ls /var/lib/tripwire/report/</userinput> and note
56the name of the newest file which starts with
57<filename>linux-</filename> and ends in <filename>.twr</filename>. This
58encrypted file was created during the last report creation and is needed
59to update the tripwire database of your system. Then, type in the
60following command making the appropriate substitutions for '?':</para>
61
62<screen><userinput>tripwire -m u -r /var/lib/tripwire/report/linux-???????-??????.twr</userinput></screen>
63
64<para>You will be placed into vim with a copy of the report in front of
65 you. If all the chnages were good, then just type
66 <userinput>:x</userinput> and after entering your local key, the
67database will be updated. If there are files which you
68 still want to be warned about, please remove the x before the filename
69 in the report and type <userinput>:x</userinput>. </para>
70
71 </sect3>
72
73 <sect3><title>Changing the Policy File</title>
74
75<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 commands:</para>
76
77<screen><userinput>twadmin -m P /etc/tripwire/twpol.txt &amp;&amp;
78tripwire -m i</userinput></screen>
79
80</sect3>
81
82</sect2>
83
Note: See TracBrowser for help on using the repository browser.