Changeset 1a95e91

Timestamp:

05/30/2022 09:25:06 PM (2 years ago)

Author:

William Harrington <kb0iic@…>

Branches:

arm

Children:

db3b722

Parents:

175a642

git-author:

Xi Ruoyao <xry111@…> (05/28/2022 01:04:22 PM)

git-committer:

William Harrington <kb0iic@…> (05/30/2022 09:25:06 PM)

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>