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