diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2022-05-28 21:04:22 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2022-05-28 21:04:22 +0800 |
| commit | 0d7dbaf24c714f272193aec650e42dd18783b867 (patch) | |
| tree | b2f431a9008ee3fb74b8fd2e0945c78b604c0fb3 | |
| parent | 0ab908d94490f34f3a5ecf3b25cf93739e5f61d0 (diff) | |
openssl: reword upgrading note for versioning scheme change
| -rw-r--r-- | chapter08/openssl.xml | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/chapter08/openssl.xml b/chapter08/openssl.xml index cece1904f..044c715a4 100644 --- a/chapter08/openssl.xml +++ b/chapter08/openssl.xml @@ -81,12 +81,15 @@ make MANSUFFIX=ssl install</userinput></screen> <note> <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> <para> |