Edit File by line

[0] Fix | Delete

[1] Fix | Delete

[2] Fix | Delete

* Licensed under the OpenSSL license (the "License"). You may not use

[3] Fix | Delete

* this file except in compliance with the License. You can obtain a copy

[4] Fix | Delete

* in the file LICENSE in the source distribution or at

[5] Fix | Delete

* https://www.openssl.org/source/license.html

[6] Fix | Delete

[7] Fix | Delete

[8] Fix | Delete

#ifndef HEADER_OPENSSLV_H

[9] Fix | Delete

# define HEADER_OPENSSLV_H

[10] Fix | Delete

[11] Fix | Delete

#ifdef __cplusplus

[12] Fix | Delete

extern "C" {

[13] Fix | Delete

#endif

[14] Fix | Delete

[15] Fix | Delete

/*-

[16] Fix | Delete

* Numeric release version identifier:

[17] Fix | Delete

* MNNFFPPS: major minor fix patch status

[18] Fix | Delete

* The status nibble has one of the values 0 for development, 1 to e for betas

[19] Fix | Delete

* 1 to 14, and f for release. The patch level is exactly that.

[20] Fix | Delete

* For example:

[21] Fix | Delete

* 0.9.3-dev 0x00903000

[22] Fix | Delete

* 0.9.3-beta1 0x00903001

[23] Fix | Delete

* 0.9.3-beta2-dev 0x00903002

[24] Fix | Delete

* 0.9.3-beta2 0x00903002 (same as ...beta2-dev)

[25] Fix | Delete

* 0.9.3 0x0090300f

[26] Fix | Delete

* 0.9.3a 0x0090301f

[27] Fix | Delete

* 0.9.4 0x0090400f

[28] Fix | Delete

* 1.2.3z 0x102031af

[29] Fix | Delete

[30] Fix | Delete

* For continuity reasons (because 0.9.5 is already out, and is coded

[31] Fix | Delete

* 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level

[32] Fix | Delete

* part is slightly different, by setting the highest bit. This means

[33] Fix | Delete

* that 0.9.5a looks like this: 0x0090581f. At 0.9.6, we can start

[34] Fix | Delete

* with 0x0090600S...

[35] Fix | Delete

[36] Fix | Delete

* (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)

[37] Fix | Delete

* (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for

[38] Fix | Delete

* major minor fix final patch/beta)

[39] Fix | Delete

[40] Fix | Delete

# define OPENSSL_VERSION_NUMBER 0x101010bfL

[41] Fix | Delete

# define OPENSSL_VERSION_TEXT "OpenSSL 1.1.1k FIPS 25 Mar 2021"

[42] Fix | Delete

[43] Fix | Delete

/*-

[44] Fix | Delete

* The macros below are to be used for shared library (.so, .dll, ...)

[45] Fix | Delete

* versioning. That kind of versioning works a bit differently between

[46] Fix | Delete

* operating systems. The most usual scheme is to set a major and a minor

[47] Fix | Delete

* number, and have the runtime loader check that the major number is equal

[48] Fix | Delete

* to what it was at application link time, while the minor number has to

[49] Fix | Delete

* be greater or equal to what it was at application link time. With this

[50] Fix | Delete

* scheme, the version number is usually part of the file name, like this:

[51] Fix | Delete

[52] Fix | Delete

* libcrypto.so.0.9

[53] Fix | Delete

[54] Fix | Delete

* Some unixen also make a softlink with the major version number only:

[55] Fix | Delete

[56] Fix | Delete

* libcrypto.so.0

[57] Fix | Delete

[58] Fix | Delete

* On Tru64 and IRIX 6.x it works a little bit differently. There, the

[59] Fix | Delete

* shared library version is stored in the file, and is actually a series

[60] Fix | Delete

* of versions, separated by colons. The rightmost version present in the

[61] Fix | Delete

* library when linking an application is stored in the application to be

[62] Fix | Delete

* matched at run time. When the application is run, a check is done to

[63] Fix | Delete

* see if the library version stored in the application matches any of the

[64] Fix | Delete

* versions in the version string of the library itself.

[65] Fix | Delete

* This version string can be constructed in any way, depending on what

[66] Fix | Delete

* kind of matching is desired. However, to implement the same scheme as

[67] Fix | Delete

* the one used in the other unixen, all compatible versions, from lowest

[68] Fix | Delete

* to highest, should be part of the string. Consecutive builds would

[69] Fix | Delete

* give the following versions strings:

[70] Fix | Delete

[71] Fix | Delete

* 3.0

[72] Fix | Delete

* 3.0:3.1

[73] Fix | Delete

* 3.0:3.1:3.2

[74] Fix | Delete

* 4.0

[75] Fix | Delete

* 4.0:4.1

[76] Fix | Delete

[77] Fix | Delete

* Notice how version 4 is completely incompatible with version, and

[78] Fix | Delete

* therefore give the breach you can see.

[79] Fix | Delete

[80] Fix | Delete

* There may be other schemes as well that I haven't yet discovered.

[81] Fix | Delete

[82] Fix | Delete

* So, here's the way it works here: first of all, the library version

[83] Fix | Delete

* number doesn't need at all to match the overall OpenSSL version.

[84] Fix | Delete

* However, it's nice and more understandable if it actually does.

[85] Fix | Delete

* The current library version is stored in the macro SHLIB_VERSION_NUMBER,

[86] Fix | Delete

* which is just a piece of text in the format "M.m.e" (Major, minor, edit).

[87] Fix | Delete

* For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,

[88] Fix | Delete

* we need to keep a history of version numbers, which is done in the

[89] Fix | Delete

* macro SHLIB_VERSION_HISTORY. The numbers are separated by colons and

[90] Fix | Delete

* should only keep the versions that are binary compatible with the current.

[91] Fix | Delete

[92] Fix | Delete

# define SHLIB_VERSION_HISTORY ""

[93] Fix | Delete

# define SHLIB_VERSION_NUMBER "1.1"

[94] Fix | Delete

[95] Fix | Delete

[96] Fix | Delete

#ifdef __cplusplus

[97] Fix | Delete

}

[98] Fix | Delete

#endif

[99] Fix | Delete

#endif /* HEADER_OPENSSLV_H */

[100] Fix | Delete

[101] Fix | Delete