Changeset b2a7072d


Ignore:
Timestamp:
09/13/2003 06:17:08 PM (19 years ago)
Author:
Larry Lawrence <larry@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 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, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/soup3, xry111/test-20220226
Children:
512e06f9
Parents:
30f1425
Message:

edits caught by Bill

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

Location:
postlfs/security
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • postlfs/security/pam/linux_pam-config.xml

    r30f1425 rb2a7072d  
    3232# End /etc/pam.conf</screen>
    3333
    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
     36fields and allowable entries.  The
    3637<ulink url="http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html">
    3738Linux-PAM guide for system administrators</ulink> and two
  • postlfs/security/tripwire/tripwire-config.xml

    r30f1425 rb2a7072d  
    2929/usr/share/doc/tripwire/policyguide.txt</filename>. <filename>twpol.txt
    3030</filename> is a good policy file for beginners as it will note any changes to
    31 the  filesystem and can even be used as an annoying way of keeping track of
     31the filesystem and can even be used as an annoying way of keeping track of
    3232changes for uninstallation of software.</para>
    3333
     
    4545
    4646<sect3><title>Usage Information</title>
    47 <para>To use tripwire after this and run a report using the following command:
     47<para>To use tripwire after this and run a report, use the following command:
    4848
    4949<screen><userinput><command>tripwire -m c &gt; /etc/tripwire/report.txt
     
    5151
    5252<para>View the output to check the integrity of your files. An automatic
    53 integrity report can be produced by using fcron. </para>
     53integrity report can be produced by using a cron facility to schedule
     54the runs. </para>
    5455
    5556<para>Please note that after you run an integrity check, you must check
Note: See TracChangeset for help on using the changeset viewer.