Gecko [ www.foryou-vip.com ]

Name	Size	Permission	Date
core.h	230 B	-rw-r--r--	2017-04-16 12:14
crypto_aead_aes256gcm.h	6.24 KB	-rw-r--r--	2017-04-16 12:14
crypto_aead_chacha20poly1305.h	7.35 KB	-rw-r--r--	2017-04-16 12:14
crypto_auth.h	950 B	-rw-r--r--	2017-04-16 12:14
crypto_auth_hmacsha256.h	1.79 KB	-rw-r--r--	2017-04-16 12:14
crypto_auth_hmacsha512.h	1.79 KB	-rw-r--r--	2017-04-16 12:14
crypto_auth_hmacsha512256.h	1.74 KB	-rw-r--r--	2017-04-16 12:14
crypto_box.h	5.9 KB	-rw-r--r--	2017-04-16 12:14
crypto_box_curve25519xsalsa20poly1305.h	3.9 KB	-rw-r--r--	2017-04-16 12:14
crypto_core_hchacha20.h	769 B	-rw-r--r--	2017-04-16 12:14
crypto_core_hsalsa20.h	757 B	-rw-r--r--	2017-04-16 12:14
crypto_core_salsa20.h	745 B	-rw-r--r--	2017-04-16 12:14
crypto_core_salsa2012.h	769 B	-rw-r--r--	2017-04-16 12:14
crypto_core_salsa208.h	757 B	-rw-r--r--	2017-04-16 12:14
crypto_generichash.h	2.03 KB	-rw-r--r--	2017-04-16 12:14
crypto_generichash_blake2b.h	3.74 KB	-rw-r--r--	2017-04-16 12:14
crypto_hash.h	872 B	-rw-r--r--	2017-04-16 12:14
crypto_hash_sha256.h	1.33 KB	-rw-r--r--	2017-04-16 12:14
crypto_hash_sha512.h	1.33 KB	-rw-r--r--	2017-04-16 12:14
crypto_int32.h	106 B	-rw-r--r--	2017-04-16 12:14
crypto_int64.h	106 B	-rw-r--r--	2017-04-16 12:14
crypto_onetimeauth.h	1.57 KB	-rw-r--r--	2017-04-16 12:14
crypto_onetimeauth_poly1305.h	1.89 KB	-rw-r--r--	2017-04-16 12:14
crypto_pwhash.h	2.68 KB	-rw-r--r--	2017-04-16 12:14
crypto_pwhash_argon2i.h	2.6 KB	-rw-r--r--	2017-04-16 12:14
crypto_pwhash_scryptsalsa208sha256.h	2.94 KB	-rw-r--r--	2017-04-16 12:14
crypto_scalarmult.h	848 B	-rw-r--r--	2017-04-16 12:14
crypto_scalarmult_curve25519.h	872 B	-rw-r--r--	2017-04-16 12:14
crypto_secretbox.h	2.74 KB	-rw-r--r--	2017-04-16 12:14
crypto_secretbox_xsalsa20poly1305.h	1.66 KB	-rw-r--r--	2017-04-16 12:14
crypto_shorthash.h	789 B	-rw-r--r--	2017-04-16 12:14
crypto_shorthash_siphash24.h	656 B	-rw-r--r--	2017-04-16 12:14
crypto_sign.h	2.14 KB	-rw-r--r--	2017-04-16 12:14
crypto_sign_ed25519.h	2.56 KB	-rw-r--r--	2017-04-16 12:14
crypto_sign_edwards25519sha512batch.h	1.78 KB	-rw-r--r--	2017-04-16 12:14
crypto_stream.h	1.24 KB	-rw-r--r--	2017-04-16 12:14
crypto_stream_aes128ctr.h	1.84 KB	-rw-r--r--	2017-04-16 12:14
crypto_stream_chacha20.h	2.52 KB	-rw-r--r--	2017-04-16 12:14
crypto_stream_salsa20.h	1.42 KB	-rw-r--r--	2017-04-16 12:14
crypto_stream_salsa2012.h	1.15 KB	-rw-r--r--	2017-04-16 12:14
crypto_stream_salsa208.h	1.14 KB	-rw-r--r--	2017-04-16 12:14
crypto_stream_xsalsa20.h	1.43 KB	-rw-r--r--	2017-04-16 12:14
crypto_uint16.h	110 B	-rw-r--r--	2017-04-16 12:14
crypto_uint32.h	110 B	-rw-r--r--	2017-04-16 12:14
crypto_uint64.h	110 B	-rw-r--r--	2017-04-16 12:14
crypto_uint8.h	106 B	-rw-r--r--	2017-04-16 12:14
crypto_verify_16.h	393 B	-rw-r--r--	2017-04-16 12:14
crypto_verify_32.h	393 B	-rw-r--r--	2017-04-16 12:14
crypto_verify_64.h	393 B	-rw-r--r--	2017-04-16 12:14
export.h	934 B	-rw-r--r--	2017-04-16 12:14
randombytes.h	1.33 KB	-rw-r--r--	2017-04-16 12:14
randombytes_salsa20_random.h	290 B	-rw-r--r--	2017-04-16 12:14
randombytes_sysrandom.h	282 B	-rw-r--r--	2017-04-16 12:14
runtime.h	729 B	-rw-r--r--	2017-04-16 12:14
utils.h	3.99 KB	-rw-r--r--	2017-04-16 12:14
version.h	450 B	-rw-r--r--	2017-04-16 12:14

Rename

#ifndef sodium_utils_H
#define sodium_utils_H

#include <stddef.h>

#include "export.h"

#ifdef __cplusplus
extern "C" {
#endif

#ifndef SODIUM_C99
# if defined(__cplusplus) || !defined(__STDC_VERSION__) || __STDC_VERSION__ < 199901L
#  define SODIUM_C99(X)
# else
#  define SODIUM_C99(X) X
# endif
#endif

SODIUM_EXPORT
void sodium_memzero(void * const pnt, const size_t len);

/*
 * WARNING: sodium_memcmp() must be used to verify if two secret keys
 * are equal, in constant time.
 * It returns 0 if the keys are equal, and -1 if they differ.
 * This function is not designed for lexicographical comparisons.
 */
SODIUM_EXPORT
int sodium_memcmp(const void * const b1_, const void * const b2_, size_t len)
            __attribute__ ((warn_unused_result));

/*
 * sodium_compare() returns -1 if b1_ < b2_, 1 if b1_ > b2_ and 0 if b1_ == b2_
 * It is suitable for lexicographical comparisons, or to compare nonces
 * and counters stored in little-endian format.
 * However, it is slower than sodium_memcmp().
 */
SODIUM_EXPORT
int sodium_compare(const unsigned char *b1_, const unsigned char *b2_,
                   size_t len)
            __attribute__ ((warn_unused_result));

SODIUM_EXPORT
int sodium_is_zero(const unsigned char *n, const size_t nlen);

SODIUM_EXPORT
void sodium_increment(unsigned char *n, const size_t nlen);

SODIUM_EXPORT
void sodium_add(unsigned char *a, const unsigned char *b, const size_t len);

SODIUM_EXPORT
char *sodium_bin2hex(char * const hex, const size_t hex_maxlen,
                     const unsigned char * const bin, const size_t bin_len);

SODIUM_EXPORT
int sodium_hex2bin(unsigned char * const bin, const size_t bin_maxlen,
                   const char * const hex, const size_t hex_len,
                   const char * const ignore, size_t * const bin_len,
                   const char ** const hex_end);

SODIUM_EXPORT
int sodium_mlock(void * const addr, const size_t len);

SODIUM_EXPORT
int sodium_munlock(void * const addr, const size_t len);

/* WARNING: sodium_malloc() and sodium_allocarray() are not general-purpose
 * allocation functions.
 *
 * They return a pointer to a region filled with 0xd0 bytes, immediately
 * followed by a guard page.
 * As a result, accessing a single byte after the requested allocation size
 * will intentionally trigger a segmentation fault.
 *
 * A canary and an additional guard page placed before the beginning of the
 * region may also kill the process if a buffer underflow is detected.
 *
 * The memory layout is:
 * [unprotected region size (read only)][guard page (no access)][unprotected pages (read/write)][guard page (no access)]
 * With the layout of the unprotected pages being:
 * [optional padding][16-bytes canary][user region]
 *
 * However:
 * - These functions are significantly slower than standard functions
 * - Each allocation requires 3 or 4 additional pages
 * - The returned address will not be aligned if the allocation size is not
 *   a multiple of the required alignment. For this reason, these functions
 *   are designed to store data, such as secret keys and messages.
 *
 * sodium_malloc() can be used to allocate any libsodium data structure,
 * with the exception of crypto_generichash_state.
 *
 * The crypto_generichash_state structure is packed and its length is
 * either 357 or 361 bytes. For this reason, when using sodium_malloc() to
 * allocate a crypto_generichash_state structure, padding must be added in
 * order to ensure proper alignment:
 * state = sodium_malloc((crypto_generichash_statebytes() + (size_t) 63U)
 *                       & ~(size_t) 63U);
 */

SODIUM_EXPORT
void *sodium_malloc(const size_t size)
            __attribute__ ((malloc));

SODIUM_EXPORT
void *sodium_allocarray(size_t count, size_t size)
            __attribute__ ((malloc));

SODIUM_EXPORT
void sodium_free(void *ptr);

SODIUM_EXPORT
int sodium_mprotect_noaccess(void *ptr);

SODIUM_EXPORT
int sodium_mprotect_readonly(void *ptr);

SODIUM_EXPORT
int sodium_mprotect_readwrite(void *ptr);

/* -------- */

int _sodium_alloc_init(void);

#ifdef __cplusplus
}
#endif

#endif