core/crypto
crypto
Constants
2COMPACT_IMPLS
COMPACT_IMPLS :: bool = #config(ODIN_CRYPTO_COMPACT, false)SourceOmit large precomputed tables, trading off performance for size.
HAS_RAND_BYTES
HAS_RAND_BYTES :: runtime.HAS_RAND_BYTESSourceHAS_RAND_BYTES is true if and only if (⟺) the runtime provides a cryptographic entropy source.
Procedures
6compare_byte_ptrs_constant_time
compare_byte_ptrs_constant_time :: proc(a: ^u8, b: ^u8, n: int) -> (int)Sourcecompare_byte_ptrs_constant_time returns 1 if and only if (⟺) the bytes pointed to by a and b are equal, 0 otherwise.
The execution time of this routine is constant regardless of the contents of the memory being compared.
compare_constant_time
compare_constant_time :: proc(a: []u8, b: []u8) -> (int)Sourcecompare_constant_time returns 1 if and only if (⟺) a and b are equal, 0 otherwise.
The execution time of this routine is constant regardless of the contents of the slices being compared, as long as the length of the slices is equal. If and only if (⟺) the length of the two slices is diferent, it will early-return 0.
is_zero_constant_time
is_zero_constant_time :: proc(b: []u8) -> (int)Sourceis_zero_constant_time returns 1 if and only if (⟺) b is all 0s, 0 otherwise.
rand_bytes
rand_bytes :: proc(dst: []u8)Sourcerand_bytes fills the dst buffer with cryptographic entropy taken from the system entropy source. This routine will block if the system entropy source is not ready yet. All system entropy source failures are treated as catastrophic, resulting in a panic.
Support for the system entropy source can be checked with the HAS_RAND_BYTES boolean constant.
random_generator
random_generator :: proc() -> (runtime.Random_Generator)Sourcerandom_generator returns a runtime.Random_Generator backed by the system entropy source.
Support for the system entropy source can be checked with the HAS_RAND_BYTES boolean constant.
zero_explicit
zero_explicit :: proc(data: rawptr, len: int) -> (rawptr)SourceSet each byte of a memory range to zero.
This procedure copies the value 0 into the len bytes of a memory range, starting at address data.
This procedure returns the pointer to data.
Unlike the zero() procedure, which can be optimized away or reordered by the compiler under certain circumstances, zero_explicit() procedure can not be optimized away or reordered with other memory access operations, and the compiler assumes volatile semantics of the memory.