Changeset b2a7072d
- Timestamp:
- 09/13/2003 06:17:08 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, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 512e06f9
- Parents:
- 30f1425
- Location:
- postlfs/security
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/security/pam/linux_pam-config.xml
r30f1425 rb2a7072d 32 32 # End /etc/pam.conf</screen> 33 33 34 <para>The <application><acronym>pam</acronym></application> man page provides a 35 good starting point for descriptions of fields and allowable entries. The 34 <para>The <application><acronym>PAM</acronym></application> man page, 35 <command>man pam</command> provides a good starting point for descriptions of 36 fields and allowable entries. The 36 37 <ulink url="http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html"> 37 38 Linux-PAM guide for system administrators</ulink> and two -
postlfs/security/tripwire/tripwire-config.xml
r30f1425 rb2a7072d 29 29 /usr/share/doc/tripwire/policyguide.txt</filename>. <filename>twpol.txt 30 30 </filename> is a good policy file for beginners as it will note any changes to 31 the 31 the filesystem and can even be used as an annoying way of keeping track of 32 32 changes for uninstallation of software.</para> 33 33 … … 45 45 46 46 <sect3><title>Usage Information</title> 47 <para>To use tripwire after this and run a report usingthe following command:47 <para>To use tripwire after this and run a report, use the following command: 48 48 49 49 <screen><userinput><command>tripwire -m c > /etc/tripwire/report.txt … … 51 51 52 52 <para>View the output to check the integrity of your files. An automatic 53 integrity report can be produced by using fcron. </para> 53 integrity report can be produced by using a cron facility to schedule 54 the runs. </para> 54 55 55 56 <para>Please note that after you run an integrity check, you must check
Note:
See TracChangeset
for help on using the changeset viewer.