diff options
Diffstat (limited to 'src/lib/libcrypto/opensslv.h')
| -rw-r--r-- | src/lib/libcrypto/opensslv.h | 89 |
1 files changed, 0 insertions, 89 deletions
diff --git a/src/lib/libcrypto/opensslv.h b/src/lib/libcrypto/opensslv.h deleted file mode 100644 index e50c1baf00..0000000000 --- a/src/lib/libcrypto/opensslv.h +++ /dev/null | |||
| @@ -1,89 +0,0 @@ | |||
| 1 | #ifndef HEADER_OPENSSLV_H | ||
| 2 | #define HEADER_OPENSSLV_H | ||
| 3 | |||
| 4 | /* Numeric release version identifier: | ||
| 5 | * MNNFFPPS: major minor fix patch status | ||
| 6 | * The status nibble has one of the values 0 for development, 1 to e for betas | ||
| 7 | * 1 to 14, and f for release. The patch level is exactly that. | ||
| 8 | * For example: | ||
| 9 | * 0.9.3-dev 0x00903000 | ||
| 10 | * 0.9.3-beta1 0x00903001 | ||
| 11 | * 0.9.3-beta2-dev 0x00903002 | ||
| 12 | * 0.9.3-beta2 0x00903002 (same as ...beta2-dev) | ||
| 13 | * 0.9.3 0x0090300f | ||
| 14 | * 0.9.3a 0x0090301f | ||
| 15 | * 0.9.4 0x0090400f | ||
| 16 | * 1.2.3z 0x102031af | ||
| 17 | * | ||
| 18 | * For continuity reasons (because 0.9.5 is already out, and is coded | ||
| 19 | * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level | ||
| 20 | * part is slightly different, by setting the highest bit. This means | ||
| 21 | * that 0.9.5a looks like this: 0x0090581f. At 0.9.6, we can start | ||
| 22 | * with 0x0090600S... | ||
| 23 | * | ||
| 24 | * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.) | ||
| 25 | * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for | ||
| 26 | * major minor fix final patch/beta) | ||
| 27 | */ | ||
| 28 | #define OPENSSL_VERSION_NUMBER 0x009070afL | ||
| 29 | #ifdef OPENSSL_FIPS | ||
| 30 | #define OPENSSL_VERSION_TEXT "OpenSSL 0.9.7j-fips 04 May 2006" | ||
| 31 | #else | ||
| 32 | #define OPENSSL_VERSION_TEXT "OpenSSL 0.9.7j 04 May 2006" | ||
| 33 | #endif | ||
| 34 | #define OPENSSL_VERSION_PTEXT " part of " OPENSSL_VERSION_TEXT | ||
| 35 | |||
| 36 | |||
| 37 | /* The macros below are to be used for shared library (.so, .dll, ...) | ||
| 38 | * versioning. That kind of versioning works a bit differently between | ||
| 39 | * operating systems. The most usual scheme is to set a major and a minor | ||
| 40 | * number, and have the runtime loader check that the major number is equal | ||
| 41 | * to what it was at application link time, while the minor number has to | ||
| 42 | * be greater or equal to what it was at application link time. With this | ||
| 43 | * scheme, the version number is usually part of the file name, like this: | ||
| 44 | * | ||
| 45 | * libcrypto.so.0.9 | ||
| 46 | * | ||
| 47 | * Some unixen also make a softlink with the major verson number only: | ||
| 48 | * | ||
| 49 | * libcrypto.so.0 | ||
| 50 | * | ||
| 51 | * On Tru64 and IRIX 6.x it works a little bit differently. There, the | ||
| 52 | * shared library version is stored in the file, and is actually a series | ||
| 53 | * of versions, separated by colons. The rightmost version present in the | ||
| 54 | * library when linking an application is stored in the application to be | ||
| 55 | * matched at run time. When the application is run, a check is done to | ||
| 56 | * see if the library version stored in the application matches any of the | ||
| 57 | * versions in the version string of the library itself. | ||
| 58 | * This version string can be constructed in any way, depending on what | ||
| 59 | * kind of matching is desired. However, to implement the same scheme as | ||
| 60 | * the one used in the other unixen, all compatible versions, from lowest | ||
| 61 | * to highest, should be part of the string. Consecutive builds would | ||
| 62 | * give the following versions strings: | ||
| 63 | * | ||
| 64 | * 3.0 | ||
| 65 | * 3.0:3.1 | ||
| 66 | * 3.0:3.1:3.2 | ||
| 67 | * 4.0 | ||
| 68 | * 4.0:4.1 | ||
| 69 | * | ||
| 70 | * Notice how version 4 is completely incompatible with version, and | ||
| 71 | * therefore give the breach you can see. | ||
| 72 | * | ||
| 73 | * There may be other schemes as well that I haven't yet discovered. | ||
| 74 | * | ||
| 75 | * So, here's the way it works here: first of all, the library version | ||
| 76 | * number doesn't need at all to match the overall OpenSSL version. | ||
| 77 | * However, it's nice and more understandable if it actually does. | ||
| 78 | * The current library version is stored in the macro SHLIB_VERSION_NUMBER, | ||
| 79 | * which is just a piece of text in the format "M.m.e" (Major, minor, edit). | ||
| 80 | * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways, | ||
| 81 | * we need to keep a history of version numbers, which is done in the | ||
| 82 | * macro SHLIB_VERSION_HISTORY. The numbers are separated by colons and | ||
| 83 | * should only keep the versions that are binary compatible with the current. | ||
| 84 | */ | ||
| 85 | #define SHLIB_VERSION_HISTORY "" | ||
| 86 | #define SHLIB_VERSION_NUMBER "0.9.7" | ||
| 87 | |||
| 88 | |||
| 89 | #endif /* HEADER_OPENSSLV_H */ | ||