Ignore:
Timestamp:
05/28/2022 01:04:22 PM (6 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
11.2, 11.2-rc1, multilib, s6-init, trunk, xry111/arm64, xry111/clfs-ng, xry111/pip3, xry111/queue-11.3, xry111/rust-wip-20221008
Children:
b4008bb
Parents:
0ab908d
Message:

openssl: reword upgrading note for versioning scheme change

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter08/openssl.xml

    r0ab908d r0d7dbaf  
    8282      <para>
    8383        You should update OpenSSL when a new version which fixes vulnerabilities
    84         is announced. The releases run in series, with a letter for each release
    85         after the initial release (e.g. 1.1.1, 1.1.1a, 1.1.1b, etc). Because LFS
    86         installs only the shared libraries, there is no need to recompile packages
    87         which link to <filename class="libraryfile">libcrypto.so</filename> or
     84        is announced.  Since OpenSSL 3.0.0, the OpenSSL versioning scheme
     85        follows the MAJOR.MINOR.PATCH format.  API/ABI compatibility
     86        are guaranteed for the same MAJOR version number.  Because LFS
     87        installs only the shared libraries, there is no need to recompile
     88        packages which link to
     89        <filename class="libraryfile">libcrypto.so</filename> or
    8890        <filename class="libraryfile">libssl.so</filename>
    89         <emphasis>when upgrading in the same series.</emphasis>
     91        <emphasis>when upgrading to a version with MAJOR version number
     92        unchanged</emphasis>.
    9093      </para>
    9194
Note: See TracChangeset for help on using the changeset viewer.