xref: /onnv-gate/usr/src/common/openssl/crypto/opensslv.h (revision 9318:704e5a016b38)
10Sstevel@tonic-gate #ifndef HEADER_OPENSSLV_H
20Sstevel@tonic-gate #define HEADER_OPENSSLV_H
30Sstevel@tonic-gate 
40Sstevel@tonic-gate /* Numeric release version identifier:
50Sstevel@tonic-gate  * MNNFFPPS: major minor fix patch status
60Sstevel@tonic-gate  * The status nibble has one of the values 0 for development, 1 to e for betas
70Sstevel@tonic-gate  * 1 to 14, and f for release.  The patch level is exactly that.
80Sstevel@tonic-gate  * For example:
90Sstevel@tonic-gate  * 0.9.3-dev	  0x00903000
100Sstevel@tonic-gate  * 0.9.3-beta1	  0x00903001
110Sstevel@tonic-gate  * 0.9.3-beta2-dev 0x00903002
120Sstevel@tonic-gate  * 0.9.3-beta2    0x00903002 (same as ...beta2-dev)
130Sstevel@tonic-gate  * 0.9.3	  0x0090300f
140Sstevel@tonic-gate  * 0.9.3a	  0x0090301f
152139Sjp161948  * 0.9.4	  0x0090400f
160Sstevel@tonic-gate  * 1.2.3z	  0x102031af
170Sstevel@tonic-gate  *
180Sstevel@tonic-gate  * For continuity reasons (because 0.9.5 is already out, and is coded
190Sstevel@tonic-gate  * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
200Sstevel@tonic-gate  * part is slightly different, by setting the highest bit.  This means
210Sstevel@tonic-gate  * that 0.9.5a looks like this: 0x0090581f.  At 0.9.6, we can start
220Sstevel@tonic-gate  * with 0x0090600S...
230Sstevel@tonic-gate  *
240Sstevel@tonic-gate  * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
250Sstevel@tonic-gate  * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
260Sstevel@tonic-gate  *  major minor fix final patch/beta)
270Sstevel@tonic-gate  */
282139Sjp161948 #define OPENSSL_VERSION_NUMBER	0x0090801fL
292139Sjp161948 #ifdef OPENSSL_FIPS
302139Sjp161948 #define OPENSSL_VERSION_TEXT	"OpenSSL 0.9.8a-fips 11 Oct 2005"
312139Sjp161948 #else
328545SJan.Pechanec@Sun.COM #define OPENSSL_VERSION_TEXT	"OpenSSL 0.9.8a 11 Oct 2005 " \
338545SJan.Pechanec@Sun.COM     "(+ security fixes for:" \
348545SJan.Pechanec@Sun.COM     " CVE-2006-2937" \
358545SJan.Pechanec@Sun.COM     " CVE-2006-2940" \
368545SJan.Pechanec@Sun.COM     " CVE-2006-3738" \
378545SJan.Pechanec@Sun.COM     " CVE-2006-4339" \
388545SJan.Pechanec@Sun.COM     " CVE-2006-4343" \
398545SJan.Pechanec@Sun.COM     " CVE-2007-3108" \
408545SJan.Pechanec@Sun.COM     " CVE-2007-4995" \
418545SJan.Pechanec@Sun.COM     " CVE-2007-5135" \
428545SJan.Pechanec@Sun.COM     " CVE-2008-5077" \
43*9318SJan.Pechanec@Sun.COM     " CVE-2009-0590" \
448545SJan.Pechanec@Sun.COM     ")"
458545SJan.Pechanec@Sun.COM 
462139Sjp161948 #endif
470Sstevel@tonic-gate #define OPENSSL_VERSION_PTEXT	" part of " OPENSSL_VERSION_TEXT
480Sstevel@tonic-gate 
490Sstevel@tonic-gate 
500Sstevel@tonic-gate /* The macros below are to be used for shared library (.so, .dll, ...)
510Sstevel@tonic-gate  * versioning.  That kind of versioning works a bit differently between
520Sstevel@tonic-gate  * operating systems.  The most usual scheme is to set a major and a minor
530Sstevel@tonic-gate  * number, and have the runtime loader check that the major number is equal
540Sstevel@tonic-gate  * to what it was at application link time, while the minor number has to
550Sstevel@tonic-gate  * be greater or equal to what it was at application link time.  With this
560Sstevel@tonic-gate  * scheme, the version number is usually part of the file name, like this:
570Sstevel@tonic-gate  *
580Sstevel@tonic-gate  *	libcrypto.so.0.9
590Sstevel@tonic-gate  *
600Sstevel@tonic-gate  * Some unixen also make a softlink with the major verson number only:
610Sstevel@tonic-gate  *
620Sstevel@tonic-gate  *	libcrypto.so.0
630Sstevel@tonic-gate  *
640Sstevel@tonic-gate  * On Tru64 and IRIX 6.x it works a little bit differently.  There, the
650Sstevel@tonic-gate  * shared library version is stored in the file, and is actually a series
660Sstevel@tonic-gate  * of versions, separated by colons.  The rightmost version present in the
670Sstevel@tonic-gate  * library when linking an application is stored in the application to be
680Sstevel@tonic-gate  * matched at run time.  When the application is run, a check is done to
690Sstevel@tonic-gate  * see if the library version stored in the application matches any of the
700Sstevel@tonic-gate  * versions in the version string of the library itself.
710Sstevel@tonic-gate  * This version string can be constructed in any way, depending on what
720Sstevel@tonic-gate  * kind of matching is desired.  However, to implement the same scheme as
730Sstevel@tonic-gate  * the one used in the other unixen, all compatible versions, from lowest
740Sstevel@tonic-gate  * to highest, should be part of the string.  Consecutive builds would
750Sstevel@tonic-gate  * give the following versions strings:
760Sstevel@tonic-gate  *
770Sstevel@tonic-gate  *	3.0
780Sstevel@tonic-gate  *	3.0:3.1
790Sstevel@tonic-gate  *	3.0:3.1:3.2
800Sstevel@tonic-gate  *	4.0
810Sstevel@tonic-gate  *	4.0:4.1
820Sstevel@tonic-gate  *
830Sstevel@tonic-gate  * Notice how version 4 is completely incompatible with version, and
840Sstevel@tonic-gate  * therefore give the breach you can see.
850Sstevel@tonic-gate  *
860Sstevel@tonic-gate  * There may be other schemes as well that I haven't yet discovered.
870Sstevel@tonic-gate  *
880Sstevel@tonic-gate  * So, here's the way it works here: first of all, the library version
890Sstevel@tonic-gate  * number doesn't need at all to match the overall OpenSSL version.
900Sstevel@tonic-gate  * However, it's nice and more understandable if it actually does.
910Sstevel@tonic-gate  * The current library version is stored in the macro SHLIB_VERSION_NUMBER,
920Sstevel@tonic-gate  * which is just a piece of text in the format "M.m.e" (Major, minor, edit).
930Sstevel@tonic-gate  * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,
940Sstevel@tonic-gate  * we need to keep a history of version numbers, which is done in the
950Sstevel@tonic-gate  * macro SHLIB_VERSION_HISTORY.  The numbers are separated by colons and
960Sstevel@tonic-gate  * should only keep the versions that are binary compatible with the current.
970Sstevel@tonic-gate  */
980Sstevel@tonic-gate #define SHLIB_VERSION_HISTORY ""
992139Sjp161948 #define SHLIB_VERSION_NUMBER "0.9.8"
1000Sstevel@tonic-gate 
1010Sstevel@tonic-gate 
1020Sstevel@tonic-gate #endif /* HEADER_OPENSSLV_H */
103