Changeset 5628618e for postlfs/security/tripwire/tripwire-config.xml
- Timestamp:
- 04/07/2003 09:14:53 PM (21 years ago)
- Branches:
- 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
- Children:
- b77b166f
- Parents:
- 0cfd5d9
- File:
-
- 1 edited
-
postlfs/security/tripwire/tripwire-config.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
postlfs/security/tripwire/tripwire-config.xml
r0cfd5d9 r5628618e 30 30 <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> 31 31 32 <para>After your policy file has been transferred to <filename>/etc/tripwire/</filename> you may begin the configu ation steps:</para>32 <para>After your policy file has been transferred to <filename>/etc/tripwire/</filename> you may begin the configuration steps:</para> 33 33 34 34 <screen><userinput>twadmin -m P /etc/tripwire/twpol.txt && … … 61 61 62 62 <para>You will be placed into vim with a copy of the report in front of 63 you. If all the ch nages were good, then just type63 you. If all the changes were good, then just type 64 64 <userinput>:x</userinput> and after entering your local key, the 65 65 database will be updated. If there are files which you
Note:
See TracChangeset
for help on using the changeset viewer.
