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