Changeset 1ad59f2 for postlfs/security

Timestamp:

05/14/2014 07:53:28 PM (10 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 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, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

aca44793

Parents:

16e2ab9

Message:

Fix compilation of tripwire with gcc-4.9.0

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

File:

• postlfs/security/tripwire.xml (modified) (4 diffs)

postlfs/security/tripwire.xml

@@ -82 +82 @@
 sed -i -e '/TWMAN/ s|${prefix}|/usr/share|' \
        -e '/TWDOCS/s|${prefix}|/usr/share|' install/install.cfg          &&
+sed -i -e 's/eArchiveOpen e\([^)]*)\)/throw ( eArchiveOpen\1 )/' \
+       -e '/throw e;/d' src/core/archive.cpp                             &&
 
 ./configure --prefix=/usr --sysconfdir=/etc/tripwire                     &&
@@ -114 +116 @@
     Fix a compilation issue with gcc-4.7.</para>
 
+    <para><command>sed ... install/install.cfg</command>:
+    Fix the location of the man and doc directories.</para>
+
+    <para><command>sed ... src/core/archive.cpp</command>:
+    Fix compilation with gcc-4.9.</para>
+
     <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>
+
+    <note><para>During <command>make install</command>, several questions
+    are asked, including passwords. If you want to make a script, you have
+    to apply a <application>sed</application> before running
+    <command>make install</command>:</para>
+
+    <para>
+    <command>sed -i -e 's@install/install.sh@&amp; -n -s<replaceable>&lt;site-password&gt;</replaceable> -l<replaceable>&lt;local-password&gt;</replaceable>@' Makefile</command>
+    </para>
+
+    <para>Of course, you should do this with dummy passwords and change them
+    later.</para></note>
 
     <para><command>cp -v policy/*.txt /usr/doc/tripwire</command>: This command
@@ -150 +170 @@
       <para>Policy files should be tailored to each individual distribution
       and/or installation. Some example policy files can be found in <filename
-      class="directory">/usr/doc/tripwire/</filename> (Note that <filename
-      class="directory">/usr/doc/</filename> is a symbolic link on LFS systems
-      to <filename class="directory">/usr/share/doc/</filename>).</para>
+      class="directory">/usr/share/doc/tripwire/</filename>.</para>
 
       <para>If desired, copy the policy file you'd like to try into <filename
@@ -158 +176 @@
       policy file, <filename>twpol.txt</filename>.  It is, however, recommended
       that you edit your policy file. Get ideas from the examples above and
-      read <filename>/usr/doc/tripwire/policyguide.txt</filename> for
+      read <filename>/usr/share/doc/tripwire/policyguide.txt</filename> for
       additional information. <filename>twpol.txt</filename> is a good policy
-      file for learning about  <application>Tripwire</application> as it will
+      file for learning about <application>Tripwire</application> 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>