Changeset 697e6ca5


Ignore:
Timestamp:
02/28/2018 04:11:20 PM (4 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, ken/refactor-virt, lazarus, perl-modules, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
b285074
Parents:
273653c
Message:

Reformat Which and make-ca to be closer to the template. Add the
lfs-checked tag to id3lib

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

Files:
3 edited

Legend:

Unmodified
Added
Removed
  • general/sysutils/which.xml

    r273653c r697e6ca5  
    2525  <title>Which-&which-version; and Alternatives</title>
    2626
     27  <para>
     28    The presence or absence of the <command>which</command> program in the
     29    main LFS book is probably one of the most contentious issues on the
     30    mailing lists. It has resulted in at least one flame war in the past. To
     31    hopefully put an end to this once and for all, presented here are two
     32    options for equipping your system with <command>which</command>. The
     33    question of which <quote><command>which</command></quote> is for you to
     34    decide.
     35  </para>
     36
    2737  <indexterm zone="which">
    2838    <primary sortas="a-Which">Which</primary>
    2939  </indexterm>
    3040
    31   <para>The presence or absence of the <command>which</command> program
    32   in the main LFS book is probably one of the most contentious issues on the
    33   mailing lists. It has resulted in at least one flame war in the past. To hopefully
    34   put an end to this once and for all, presented here are two options for equipping
    35   your system with <command>which</command>. The question of which
    36   <quote><command>which</command></quote> is for you to decide.</para>
     41  <sect2 role="package">
     42    <title>Introduction to GNU Which</title>
    3743
    38   <para>The first option is to install the actual GNU
    39   <application>which</application> package.</para>
     44    <para>
     45      The first option is to install the actual GNU
     46      <application>which</application> package.
     47    </para>
    4048
    41   &lfs82_checked;
    42 
    43   <sect2 role="package">
    44     <title>Introduction to Which</title>
     49    &lfs82_checked;
    4550
    4651    <bridgehead renderas="sect3">Package Information</bridgehead>
  • multimedia/libdriv/id3lib.xml

    r273653c r697e6ca5  
    3232    <para><application>id3lib</application> is a library for reading,
    3333    writing and manipulating id3v1 and id3v2 multimedia data containers.</para>
     34
     35    &lfs82_checked;
    3436
    3537    <bridgehead renderas="sect3">Package Information</bridgehead>
     
    8587make</userinput></screen>
    8688
    87     <para>This packages does not come wiht a working test suite.</para>
     89    <para>This packages does not come with a working test suite.</para>
    8890
    8991    <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
  • postlfs/security/make-ca.xml

    r273653c r697e6ca5  
    1515]>
    1616
    17 <sect1 id="make-ca" xreflabel="make-ca">
     17<sect1 id="make-ca" xreflabel="make-ca-&make-ca-version;">
    1818  <?dbhtml filename="make-ca.html"?>
    1919
     
    2323  </sect1info>
    2424
    25   <title>make-ca</title>
    26 
    27   <para>Public Key Infrastructure (PKI) is a method to validate the
    28   authenticity of an otherwise unknown entity across untrusted networks. PKI
    29   works by establishing a chain of trust, rather than trusting each individual
    30   host or entity explicitly. In order for a certificate presented by a remote
    31   entity to be trusted, that certificate must present a complete chain of
    32   certificates that can be validated using the root certificate of a
    33   Certificate Authority (CA) that is trusted by the local machine.</para>
    34  
    35   <para>Establishing trust with a CA involves validating things like company
    36   address, ownership, contact information, etc., and ensuring that the CA has
    37   followed best practices, such as undergoing periodic security audits by
    38   independent investigators and maintaining an always available certificate
    39   revocation list. This is well outside the scope of BLFS (as it is for most
    40   Linux distributions). The certificate store provided here is taken from the
    41   Mozilla Foundation, who have established very strict inclusion policies
    42   described
    43   <ulink url="https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/">here</ulink>.</para>
    44 
    45   &lfs82_checked;
    46 
     25  <title>make-ca-&make-ca-version;</title>
    4726  <indexterm zone="make-ca">
    4827    <primary sortas="a-make-ca">make-ca</primary>
     
    5231    <title>Introduction to make-ca</title>
    5332
    54    <bridgehead renderas="sect3">Package Information</bridgehead>
     33    <para>
     34      Public Key Infrastructure (PKI) is a method to validate the authenticity
     35      of an otherwise unknown entity across untrusted networks. PKI works by
     36      establishing a chain of trust, rather than trusting each individual host
     37      or entity explicitly. In order for a certificate presented by a remote
     38      entity to be trusted, that certificate must present a complete chain of
     39      certificates that can be validated using the root certificate of a
     40      Certificate Authority (CA) that is trusted by the local machine.
     41    </para>
     42 
     43    <para>
     44      Establishing trust with a CA involves validating things like company
     45      address, ownership, contact information, etc., and ensuring that the CA
     46      has followed best practices, such as undergoing periodic security audits
     47      by independent investigators and maintaining an always available
     48      certificate revocation list. This is well outside the scope of BLFS (as
     49      it is for most Linux distributions). The certificate store provided here
     50      is taken from the Mozilla Foundation, who have established very strict
     51      inclusion policies described <ulink
     52        url="https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/">here</ulink>.
     53    </para>
     54
     55  &lfs82_checked;
     56
     57    <bridgehead renderas="sect3">Package Information</bridgehead>
    5558    <itemizedlist spacing="compact">
    5659      <listitem>
Note: See TracChangeset for help on using the changeset viewer.