Lines Matching +full:data +full:- +full:lanes

5 EVP_KDF-ARGON2 - The Argon2 EVP KDF implementation
9 Support for computing the B<argon2> password-based KDF through the B<EVP_KDF>
12 The EVP_KDF-ARGON2 algorithm implements the Argon2 password-based key
13 derivation function, as described in IETF RFC 9106.  It is memory-hard in
19 Argon2d (Argon2i) uses data-dependent (data-independent) memory access and
20 primary seek to address trade-off (side-channel) attacks.
23 pass, generates reference addresses data-independently as in Argon2i, whereas
24 in later slices and next passes it generates them data-dependently as in
27 Sbox-hardened version Argon2ds is not supported.
55 Note that secret (or pepper) is an optional secret data used along the
60 The number of threads, bounded above by the number of lanes.
62 This can only be used with built-in thread support. Threading must be
67 Optional associated data, may be used to "tag" a group of keys, or tie them
70 =item "lanes" (B<OSSL_KDF_PARAM_ARGON2_LANES>) <unsigned integer>
72 Argon2 splits the requested memory size into lanes, each of which is designed
74 recommended to use p lanes.
76 The number of lanes is used to derive the key. It is possible to specify
77 more lanes than the number of available computational threads. This is
78 especially encouraged if multi-threading is disabled.
92 Otherwise, they are zeroed along the rest of Argon2 context data on clear,
103 using 2 lanes, 2 threads, and memory cost of 65536:
120      uint32_t lanes = 2, threads = 2, memcost = 65536;
134                                         &lanes);
170 RFC 9106 Argon2, see L<https://www.rfc-editor.org/rfc/rfc9106.txt>.
187 Copyright 2022-2024 The OpenSSL Project Authors. All Rights Reserved.