Gecko [ edgpens.lpkmn.gov.my ]

Name	Size	Permission
aes.h	5.69 KB	-rw-rw-rw-
asn1.h	49.04 KB	-rw-rw-rw-
asn1_mac.h	18.51 KB	-rw-rw-rw-
asn1t.h	28.29 KB	-rw-rw-rw-
bio.h	31.14 KB	-rw-rw-rw-
blowfish.h	5.18 KB	-rw-rw-rw-
bn.h	33.61 KB	-rw-rw-rw-
buffer.h	4.46 KB	-rw-rw-rw-
cast.h	4.49 KB	-rw-rw-rw-
comp.h	1.93 KB	-rw-rw-rw-
conf.h	9.26 KB	-rw-rw-rw-
conf_api.h	3.98 KB	-rw-rw-rw-
crypto.h	24.25 KB	-rw-rw-rw-
des.h	10.48 KB	-rw-rw-rw-
des_old.h	17.81 KB	-rw-rw-rw-
dh.h	8.69 KB	-rw-rw-rw-
dsa.h	11.72 KB	-rw-rw-rw-
dso.h	15.87 KB	-rw-rw-rw-
dtls1.h	7.63 KB	-rw-rw-rw-
e_os2.h	9.41 KB	-rw-rw-rw-
ebcdic.h	540 B	-rw-rw-rw-
ec.h	20.89 KB	-rw-rw-rw-
ecdh.h	4.5 KB	-rw-rw-rw-
ecdsa.h	10.33 KB	-rw-rw-rw-
engine.h	38.5 KB	-rw-rw-rw-
err.h	12.97 KB	-rw-rw-rw-
evp.h	38.76 KB	-rw-rw-rw-
hmac.h	4.43 KB	-rw-rw-rw-
idea.h	4.47 KB	-rw-rw-rw-
krb5_asn.h	7.46 KB	-rw-rw-rw-
kssl.h	5.79 KB	-rw-rw-rw-
lhash.h	7.25 KB	-rw-rw-rw-
md2.h	3.96 KB	-rw-rw-rw-
md4.h	4.73 KB	-rw-rw-rw-
md5.h	4.73 KB	-rw-rw-rw-
obj_mac.h	133.3 KB	-rw-rw-rw-
objects.h	32.61 KB	-rw-rw-rw-
ocsp.h	23.5 KB	-rw-rw-rw-
opensslconf.h	7.15 KB	-rw-rw-rw-
opensslv.h	3.75 KB	-rw-rw-rw-
ossl_typ.h	6.74 KB	-rw-rw-rw-
pem.h	28.35 KB	-rw-rw-rw-
pem2.h	2.8 KB	-rw-rw-rw-
pkcs12.h	12.98 KB	-rw-rw-rw-
pkcs7.h	15.95 KB	-rw-rw-rw-
pq_compat.h	6.22 KB	-rw-rw-rw-
pqueue.h	3.56 KB	-rw-rw-rw-
rand.h	6.26 KB	-rw-rw-rw-
rc2.h	4.4 KB	-rw-rw-rw-
rc4.h	3.81 KB	-rw-rw-rw-
ripemd.h	4.36 KB	-rw-rw-rw-
rsa.h	19.6 KB	-rw-rw-rw-
safestack.h	136.29 KB	-rw-rw-rw-
sha.h	7.42 KB	-rw-rw-rw-
ssl.h	86.37 KB	-rw-rw-rw-
ssl2.h	10.46 KB	-rw-rw-rw-
ssl23.h	3.66 KB	-rw-rw-rw-
ssl3.h	23.03 KB	-rw-rw-rw-
stack.h	4.31 KB	-rw-rw-rw-
store.h	26.4 KB	-rw-rw-rw-
symhacks.h	21.67 KB	-rw-rw-rw-
tls1.h	19.42 KB	-rw-rw-rw-
tmdiff.h	4.02 KB	-rw-rw-rw-
txt_db.h	4.2 KB	-rw-rw-rw-
ui.h	16.03 KB	-rw-rw-rw-
ui_compat.h	3.36 KB	-rw-rw-rw-
x509.h	48.67 KB	-rw-rw-rw-
x509_vfy.h	20.9 KB	-rw-rw-rw-
x509v3.h	30.28 KB	-rw-rw-rw-

Code Editor : opensslv.h

#ifndef HEADER_OPENSSLV_H
#define HEADER_OPENSSLV_H

/* Numeric release version identifier:
 * MNNFFPPS: major minor fix patch status
 * The status nibble has one of the values 0 for development, 1 to e for betas
 * 1 to 14, and f for release.  The patch level is exactly that.
 * For example:
 * 0.9.3-dev	  0x00903000
 * 0.9.3-beta1	  0x00903001
 * 0.9.3-beta2-dev 0x00903002
 * 0.9.3-beta2    0x00903002 (same as ...beta2-dev)
 * 0.9.3	  0x0090300f
 * 0.9.3a	  0x0090301f
 * 0.9.4	  0x0090400f
 * 1.2.3z	  0x102031af
 *
 * For continuity reasons (because 0.9.5 is already out, and is coded
 * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
 * part is slightly different, by setting the highest bit.  This means
 * that 0.9.5a looks like this: 0x0090581f.  At 0.9.6, we can start
 * with 0x0090600S...
 *
 * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
 * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
 *  major minor fix final patch/beta)
 */
#define OPENSSL_VERSION_NUMBER	0x0090812fL
#ifdef OPENSSL_FIPS
#define OPENSSL_VERSION_TEXT	"OpenSSL 0.9.8r-fips 8 Feb 2011"
#else
#define OPENSSL_VERSION_TEXT	"OpenSSL 0.9.8r 8 Feb 2011"
#endif
#define OPENSSL_VERSION_PTEXT	" part of " OPENSSL_VERSION_TEXT

/* The macros below are to be used for shared library (.so, .dll, ...)
 * versioning.  That kind of versioning works a bit differently between
 * operating systems.  The most usual scheme is to set a major and a minor
 * number, and have the runtime loader check that the major number is equal
 * to what it was at application link time, while the minor number has to
 * be greater or equal to what it was at application link time.  With this
 * scheme, the version number is usually part of the file name, like this:
 *
 *	libcrypto.so.0.9
 *
 * Some unixen also make a softlink with the major verson number only:
 *
 *	libcrypto.so.0
 *
 * On Tru64 and IRIX 6.x it works a little bit differently.  There, the
 * shared library version is stored in the file, and is actually a series
 * of versions, separated by colons.  The rightmost version present in the
 * library when linking an application is stored in the application to be
 * matched at run time.  When the application is run, a check is done to
 * see if the library version stored in the application matches any of the
 * versions in the version string of the library itself.
 * This version string can be constructed in any way, depending on what
 * kind of matching is desired.  However, to implement the same scheme as
 * the one used in the other unixen, all compatible versions, from lowest
 * to highest, should be part of the string.  Consecutive builds would
 * give the following versions strings:
 *
 *	3.0
 *	3.0:3.1
 *	3.0:3.1:3.2
 *	4.0
 *	4.0:4.1
 *
 * Notice how version 4 is completely incompatible with version, and
 * therefore give the breach you can see.
 *
 * There may be other schemes as well that I haven't yet discovered.
 *
 * So, here's the way it works here: first of all, the library version
 * number doesn't need at all to match the overall OpenSSL version.
 * However, it's nice and more understandable if it actually does.
 * The current library version is stored in the macro SHLIB_VERSION_NUMBER,
 * which is just a piece of text in the format "M.m.e" (Major, minor, edit).
 * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,
 * we need to keep a history of version numbers, which is done in the
 * macro SHLIB_VERSION_HISTORY.  The numbers are separated by colons and
 * should only keep the versions that are binary compatible with the current.
 */
#define SHLIB_VERSION_HISTORY ""
#define SHLIB_VERSION_NUMBER "0.9.8"

#endif /* HEADER_OPENSSLV_H */

${this.title}

Code Editor : opensslv.h