Changeset 0d7dbaf

Timestamp:

05/28/2022 01:04:22 PM (23 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

b4008bb

Parents:

0ab908d

Message:

openssl: reword upgrading note for versioning scheme change

File:

• chapter08/openssl.xml (modified) (1 diff)

chapter08/openssl.xml

@@ -82 +82 @@
       <para>
         You should update OpenSSL when a new version which fixes vulnerabilities
-        is announced. The releases run in series, with a letter for each release
-        after the initial release (e.g. 1.1.1, 1.1.1a, 1.1.1b, etc). Because LFS
-        installs only the shared libraries, there is no need to recompile packages
-        which link to <filename class="libraryfile">libcrypto.so</filename> or
+        is announced.  Since OpenSSL 3.0.0, the OpenSSL versioning scheme
+        follows the MAJOR.MINOR.PATCH format.  API/ABI compatibility
+        are guaranteed for the same MAJOR version number.  Because LFS
+        installs only the shared libraries, there is no need to recompile
+        packages which link to
+        <filename class="libraryfile">libcrypto.so</filename> or
         <filename class="libraryfile">libssl.so</filename>
-        <emphasis>when upgrading in the same series.</emphasis>
+        <emphasis>when upgrading to a version with MAJOR version number
+        unchanged</emphasis>.
       </para>