"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "include/openssl/opensslv.h" between
openssl-1.1.1o.tar.gz and openssl-1.1.1p.tar.gz

About: OpenSSL is a toolkit implementing the Transport Layer Security (TLS) protocols (including SSLv3) as well as a full-strength general purpose cryptographic library. Long Term Support (LTS) version (includes support for TLSv1.3).

opensslv.h  (openssl-1.1.1o):opensslv.h  (openssl-1.1.1p)
skipping to change at line 42 skipping to change at line 42
* For continuity reasons (because 0.9.5 is already out, and is coded * For continuity reasons (because 0.9.5 is already out, and is coded
* 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
* part is slightly different, by setting the highest bit. This means * part is slightly different, by setting the highest bit. This means
* that 0.9.5a looks like this: 0x0090581f. At 0.9.6, we can start * that 0.9.5a looks like this: 0x0090581f. At 0.9.6, we can start
* with 0x0090600S... * with 0x0090600S...
* *
* (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.) * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
* (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
* major minor fix final patch/beta) * major minor fix final patch/beta)
*/ */
# define OPENSSL_VERSION_NUMBER 0x101010ffL # define OPENSSL_VERSION_NUMBER 0x1010110fL
# define OPENSSL_VERSION_TEXT "OpenSSL 1.1.1o 3 May 2022" # define OPENSSL_VERSION_TEXT "OpenSSL 1.1.1p 21 Jun 2022"
/*- /*-
* The macros below are to be used for shared library (.so, .dll, ...) * The macros below are to be used for shared library (.so, .dll, ...)
* versioning. That kind of versioning works a bit differently between * versioning. That kind of versioning works a bit differently between
* operating systems. The most usual scheme is to set a major and a minor * operating systems. The most usual scheme is to set a major and a minor
* number, and have the runtime loader check that the major number is equal * number, and have the runtime loader check that the major number is equal
* to what it was at application link time, while the minor number has to * to what it was at application link time, while the minor number has to
* be greater or equal to what it was at application link time. With this * be greater or equal to what it was at application link time. With this
* scheme, the version number is usually part of the file name, like this: * scheme, the version number is usually part of the file name, like this:
* *
 End of changes. 1 change blocks. 
2 lines changed or deleted 2 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)