Lines Matching full:s0
190 hidden entirely by defining \fB\s-1OPENSSL_API_COMPAT\s0\fR with a suitable version value,
199 \&\fB\s-1EVP_PKEY\s0\fR is a generic structure to hold diverse types of asymmetric keys
203 backends, such as providers (through \s-1\fBEVP_KEYMGMT\s0\fR\|(3)) or \fB\s-1ENGINE\s0\fRs.
205 Conceptually, an \fB\s-1EVP_PKEY\s0\fR internal key may hold a private key, a public
211 \&\fB\s-1EVP_PKEY\s0\fR has also been used for \s-1MAC\s0 algorithm that were conceived as
213 \&\*(L"SIPHASH\*(R", \*(L"HMAC\*(R", \*(L"CMAC\*(R".\s0 This usage is considered legacy and is dis…
214 in favor of the \s-1\fBEVP_MAC\s0\fR\|(3) \s-1API.\s0
216 The \fBEVP_PKEY_new()\fR function allocates an empty \fB\s-1EVP_PKEY\s0\fR structure which is
222 \&\fBEVP_PKEY_dup()\fR duplicates the \fIkey\fR. The \fIkey\fR must not be \s-1ENGINE\s0 based or
226 count is zero, frees it up. If \fIkey\fR is \s-1NULL,\s0 nothing is done.
228 \&\fBEVP_PKEY_new_raw_private_key_ex()\fR allocates a new \fB\s-1EVP_PKEY\s0\fR. Unless an
233 \&\*(L"X25519\*(R", \*(L"\s-1ED25519\*(R", \*(L"X448\*(R"\s0 or \*(L"\s-1ED448\*(R".\s0 \fIkey\fR p…
234 data for this \fB\s-1EVP_PKEY\s0\fR which should be of length \fIkeylen\fR. The length
242 \&\fB\s-1EVP_PKEY\s0\fR structure is associated with the engine \fIe\fR. The \fItype\fR argument
243 indicates what kind of key this is. The value should be a \s-1NID\s0 for a public key
244 algorithm that supports raw private keys, i.e. one of \fB\s-1EVP_PKEY_X25519\s0\fR,
245 \&\fB\s-1EVP_PKEY_ED25519\s0\fR, \fB\s-1EVP_PKEY_X448\s0\fR or \fB\s-1EVP_PKEY_ED448\s0\fR.
249 …MAC\*(R", \*(L"POLY1305\*(R", \*(L"SIPHASH\*(R",\s0 or their \s-1NID\s0 form \fB\s-1EVP_PKEY_POLY1…
250 \&\fB\s-1EVP_PKEY_SIPHASH\s0\fR, \fB\s-1EVP_PKEY_HMAC\s0\fR are also accepted. This usage is,
251 as mentioned above, discouraged in favor of the \s-1\fBEVP_MAC\s0\fR\|(3) \s-1API.\s0
255 public key data. The \fB\s-1EVP_PKEY\s0\fR structure will be initialised without any
257 \&\*(L"X25519\*(R", \*(L"\s-1ED25519\*(R", \*(L"X448\*(R"\s0 or \*(L"\s-1ED448\*(R".\s0
261 data. The \fB\s-1EVP_PKEY\s0\fR structure will be initialised without any private key
263 \&\fB\s-1EVP_PKEY_X25519\s0\fR, \fB\s-1EVP_PKEY_ED25519\s0\fR, \fB\s-1EVP_PKEY_X448\s0\fR or \fB\s-…
271 actually written. If the buffer \fIpriv\fR is \s-1NULL\s0 then \fI*len\fR is populated with
275 Currently this is: \fB\s-1EVP_PKEY_HMAC\s0\fR, \fB\s-1EVP_PKEY_POLY1305\s0\fR, \fB\s-1EVP_PKEY_SIPH…
276 \&\fB\s-1EVP_PKEY_X25519\s0\fR, \fB\s-1EVP_PKEY_ED25519\s0\fR, \fB\s-1EVP_PKEY_X448\s0\fR or \fB\s-…
281 actually written. If the buffer \fIpub\fR is \s-1NULL\s0 then \fI*len\fR is populated with
285 Currently this is: \fB\s-1EVP_PKEY_X25519\s0\fR, \fB\s-1EVP_PKEY_ED25519\s0\fR, \fB\s-1EVP_PKEY_X44…
286 \&\fB\s-1EVP_PKEY_ED448\s0\fR.
289 except it is only for the \fB\s-1EVP_PKEY_CMAC\s0\fR algorithm type. In addition to the
291 creation of a \s-1CMAC\s0 in the \fBcipher\fR argument. The cipher should be a standard
292 encryption-only cipher. For example \s-1AEAD\s0 and \s-1XTS\s0 ciphers should not be used.
294 Applications should use the \s-1\fBEVP_MAC\s0\fR\|(3) \s-1API\s0 instead
295 and set the \fB\s-1OSSL_MAC_PARAM_CIPHER\s0\fR parameter on the \fB\s-1EVP_MAC_CTX\s0\fR object
299 The \fB\s-1EVP_PKEY\s0\fR structure is used by various OpenSSL functions which require a
310 allocated \fB\s-1EVP_PKEY\s0\fR structure or \s-1NULL\s0 if an error occurred.
312 \&\fBEVP_PKEY_dup()\fR returns the key duplicate or \s-1NULL\s0 if an error occurred.
338 The documentation of \fB\s-1EVP_PKEY\s0\fR was amended in OpenSSL 3.0 to allow there to
347 in the file \s-1LICENSE\s0 in the source distribution or at