File Manager

Hackfut Security File Manager

Current Path: /usr/include/openssl

📁 ..
📄 aes.h(5.38 KB)
📄 asn1.h(51.19 KB)
📄 asn1_mac.h(18.69 KB)
📄 asn1t.h(29.39 KB)
📄 bio.h(32.21 KB)
📄 blowfish.h(5.02 KB)
📄 bn.h(32.87 KB)
📄 buffer.h(4.54 KB)
📄 camellia.h(4.84 KB)
📄 cast.h(4.39 KB)
📄 cmac.h(3.17 KB)
📄 cms.h(19.46 KB)
📄 comp.h(1.93 KB)
📄 conf.h(9.62 KB)
📄 conf_api.h(3.98 KB)
📄 crypto.h(23.97 KB)
📄 des.h(10.48 KB)
📄 des_old.h(17.81 KB)
📄 dh.h(9.96 KB)
📄 dsa.h(12.74 KB)
📄 dso.h(17.67 KB)
📄 dtls1.h(7.88 KB)
📄 e_os2.h(10.2 KB)
📄 ebcdic.h(540 B)
📄 ec.h(41.78 KB)
📄 ecdh.h(4.61 KB)
📄 ecdsa.h(10.26 KB)
📄 engine.h(39.63 KB)
📄 err.h(15.49 KB)
📄 evp.h(51.48 KB)
📄 fips.h(10.43 KB)
📄 fips_rand.h(5.38 KB)
📄 hmac.h(4.37 KB)
📄 idea.h(4.36 KB)
📄 krb5_asn.h(7.46 KB)
📄 kssl.h(5.92 KB)
📄 lhash.h(8.88 KB)
📄 md2.h(3.87 KB)
📄 md4.h(4.58 KB)
📄 md5.h(4.58 KB)
📄 modes.h(5.49 KB)
📄 obj_mac.h(133.02 KB)
📄 objects.h(35.78 KB)
📄 ocsp.h(23.48 KB)
📄 opensslconf-x86_64.h(7.17 KB)
📄 opensslconf.h(1.18 KB)
📄 opensslv.h(3.67 KB)
📄 ossl_typ.h(7.22 KB)
📄 pem.h(21.48 KB)
📄 pem2.h(2.8 KB)
📄 pkcs12.h(12.36 KB)
📄 pkcs7.h(17.64 KB)
📄 pqueue.h(3.5 KB)
📄 rand.h(6.13 KB)
📄 rc2.h(4.3 KB)
📄 rc4.h(3.71 KB)
📄 ripemd.h(4.23 KB)
📄 rsa.h(22.8 KB)
📄 safestack.h(179.84 KB)
📄 seed.h(5.58 KB)
📄 sha.h(7.19 KB)
📄 srtp.h(6.49 KB)
📄 ssl.h(99.85 KB)
📄 ssl2.h(10.5 KB)
📄 ssl23.h(3.66 KB)
📄 ssl3.h(26.3 KB)
📄 stack.h(4.31 KB)
📄 symhacks.h(23.38 KB)
📄 tls1.h(34.33 KB)
📄 ts.h(30.28 KB)
📄 txt_db.h(4.38 KB)
📄 ui.h(16.27 KB)
📄 ui_compat.h(3.36 KB)
📄 whrlpool.h(1019 B)
📄 x509.h(44.05 KB)
📄 x509_vfy.h(21.95 KB)
📄 x509v3.h(31.95 KB)

Editing: 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	0x1000105fL
#ifdef OPENSSL_FIPS
#define OPENSSL_VERSION_TEXT	"OpenSSL 1.0.1e-fips 11 Feb 2013"
#else
#define OPENSSL_VERSION_TEXT	"OpenSSL 1.0.1e 11 Feb 2013"
#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 "1.0.1e"

#endif /* HEADER_OPENSSLV_H */

Hackfut Security File Manager

Editing: opensslv.h

Upload File

Create Folder