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