File Manager

X7ROOT File Manager

Current Path: /opt/alt/openssl/include/openssl

opt / alt / openssl / include / openssl /

ðŸ“ ..
ðŸ“„ aes.h(6 KB)
ðŸ“„ asn1.h(61.91 KB)
ðŸ“„ asn1_mac.h(23.86 KB)
ðŸ“„ asn1t.h(33.67 KB)
ðŸ“„ bio.h(37.83 KB)
ðŸ“„ blowfish.h(5.23 KB)
ðŸ“„ bn.h(42.79 KB)
ðŸ“„ buffer.h(4.91 KB)
ðŸ“„ camellia.h(5.43 KB)
ðŸ“„ cast.h(4.55 KB)
ðŸ“„ cmac.h(3.18 KB)
ðŸ“„ cms.h(27.97 KB)
ðŸ“„ comp.h(2.32 KB)
ðŸ“„ conf.h(11.05 KB)
ðŸ“„ conf_api.h(4.05 KB)
ðŸ“„ crypto.h(27.23 KB)
ðŸ“„ des.h(11.49 KB)
ðŸ“„ des_old.h(20.98 KB)
ðŸ“„ dh.h(16.46 KB)
ðŸ“„ dsa.h(14.85 KB)
ðŸ“„ dso.h(19.74 KB)
ðŸ“„ dtls1.h(8.83 KB)
ðŸ“„ e_os2.h(10.69 KB)
ðŸ“„ ebcdic.h(616 B)
ðŸ“„ ec.h(54.75 KB)
ðŸ“„ ecdh.h(5.07 KB)
ðŸ“„ ecdsa.h(13.71 KB)
ðŸ“„ engine.h(43.89 KB)
ðŸ“„ err.h(16.46 KB)
ðŸ“„ evp.h(71.85 KB)
ðŸ“„ fips.h(13.31 KB)
ðŸ“„ fips_rand.h(7.11 KB)
ðŸ“„ hmac.h(4.43 KB)
ðŸ“„ idea.h(4.57 KB)
ðŸ“„ krb5_asn.h(7.97 KB)
ðŸ“„ kssl.h(6.69 KB)
ðŸ“„ lhash.h(9.33 KB)
ðŸ“„ md2.h(3.89 KB)
ðŸ“„ md4.h(4.67 KB)
ðŸ“„ md5.h(4.67 KB)
ðŸ“„ modes.h(8.46 KB)
ðŸ“„ obj_mac.h(171.54 KB)
ðŸ“„ objects.h(46.45 KB)
ðŸ“„ ocsp.h(26.51 KB)
ðŸ“„ opensslconf-x86_64.h(7.92 KB)
ðŸ“„ opensslconf.h(1.54 KB)
ðŸ“„ opensslv.h(3.85 KB)
ðŸ“„ ossl_typ.h(7.65 KB)
ðŸ“„ pem.h(25.33 KB)
ðŸ“„ pem2.h(2.79 KB)
ðŸ“„ pkcs12.h(14.5 KB)
ðŸ“„ pkcs7.h(20.29 KB)
ðŸ“„ pqueue.h(3.59 KB)
ðŸ“„ rand.h(6.73 KB)
ðŸ“„ rc2.h(4.44 KB)
ðŸ“„ rc4.h(3.72 KB)
ðŸ“„ rc5.h(4.82 KB)
ðŸ“„ ripemd.h(4.27 KB)
ðŸ“„ rsa.h(29.68 KB)
ðŸ“„ safestack.h(198.15 KB)
ðŸ“„ seed.h(5.9 KB)
ðŸ“„ sha.h(7.4 KB)
ðŸ“„ srtp.h(6.48 KB)
ðŸ“„ ssl.h(145.83 KB)
ðŸ“„ ssl2.h(11.77 KB)
ðŸ“„ ssl23.h(3.7 KB)
ðŸ“„ ssl3.h(32.5 KB)
ðŸ“„ stack.h(4.43 KB)
ðŸ“„ symhacks.h(27.17 KB)
ðŸ“„ tls1.h(38.49 KB)
ðŸ“„ ts.h(33.75 KB)
ðŸ“„ txt_db.h(4.52 KB)
ðŸ“„ ui.h(18.25 KB)
ðŸ“„ ui_compat.h(3.41 KB)
ðŸ“„ whrlpool.h(1.06 KB)
ðŸ“„ x509.h(52.07 KB)
ðŸ“„ x509_vfy.h(28.55 KB)
ðŸ“„ x509v3.h(39.44 KB)

Editing: opensslv.h

#ifndef HEADER_OPENSSLV_H
# define HEADER_OPENSSLV_H

#ifdef  __cplusplus
extern "C" {
#endif

/*-
 * 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  0x1000215fL
# ifdef OPENSSL_FIPS
#  define OPENSSL_VERSION_TEXT    "OpenSSL 1.0.2u-fips  20 Dec 2019"
# else
#  define OPENSSL_VERSION_TEXT    "OpenSSL 1.0.2u  20 Dec 2019"
# 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.2u"

#ifdef  __cplusplus
}
#endif
#endif                          /* HEADER_OPENSSLV_H */

X7ROOT File Manager

Editing: opensslv.h

Upload File

Create Folder