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

1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "EVP_KDF-ARGON2 7ossl"
58 .TH EVP_KDF-ARGON2 7ossl 2025-09-30 3.5.4 OpenSSL
64 EVP_KDF\-ARGON2 \- The Argon2 EVP KDF implementation
67 Support for computing the \fBargon2\fR password-based KDF through the \fBEVP_KDF\fR
70 The EVP_KDF\-ARGON2 algorithm implements the Argon2 password-based key
71 derivation function, as described in IETF RFC 9106.  It is memory-hard in
77 Argon2d (Argon2i) uses data-dependent (data-independent) memory access and
78 primary seek to address trade-off (side-channel) attacks.
81 pass, generates reference addresses data-independently as in Argon2i, whereas
82 in later slices and next passes it generates them data-dependently as in
85 Sbox-hardened version Argon2ds is not supported.
111 Note that secret (or pepper) is an optional secret data used along the
115 The number of threads, bounded above by the number of lanes.
117 This can only be used with built-in thread support. Threading must be
121 Optional associated data, may be used to "tag" a group of keys, or tie them
123 .IP """lanes"" (\fBOSSL_KDF_PARAM_ARGON2_LANES\fR) <unsigned integer>" 4
124 .IX Item """lanes"" (OSSL_KDF_PARAM_ARGON2_LANES) <unsigned integer>"
125 Argon2 splits the requested memory size into lanes, each of which is designed
127 recommended to use p lanes.
129 The number of lanes is used to derive the key. It is possible to specify
130 more lanes than the number of available computational threads. This is
131 especially encouraged if multi-threading is disabled.
142 Otherwise, they are zeroed along the rest of Argon2 context data on clear,
150 using 2 lanes, 2 threads, and memory cost of 65536:
168 \&     uint32_t lanes = 2, threads = 2, memcost = 65536;
182 \&                                        &lanes);
217 RFC 9106 Argon2, see <https://www.rfc\-editor.org/rfc/rfc9106.txt>.
231 Copyright 2022\-2024 The OpenSSL Project Authors. All Rights Reserved.