Lines Matching refs:private
18 - public/private key allocation and raw key handling functions
68 Conceptually, an B<EVP_PKEY> internal key may hold a private key, a public
71 be made; for example, signing normally requires the presence of a private key,
74 =for comment ED signature require both the private and public key...
82 used by OpenSSL to store public and private keys. The reference count is set to
97 string for a public key algorithm that supports raw private keys, i.e one of
98 "X25519", "ED25519", "X448" or "ED448". I<key> points to the raw private key
101 automatically derived from the given private key data (if appropriate for the
109 algorithm that supports raw private keys, i.e. one of B<EVP_PKEY_X25519>,
121 private key information. Algorithm types that support raw public keys are
126 data. The B<EVP_PKEY> structure will be initialised without any private key
134 private key data. The size of the I<priv> buffer should be in I<*len> on entry
138 responsible for ensuring that the buffer is large enough to receive the private
139 key data. This function only works for algorithms that support raw private keys.
155 raw private key data, it also takes a cipher algorithm to be used during
166 general private key without reference to any particular algorithm.
168 The structure returned by EVP_PKEY_new() is empty. To add a private or public
208 be the private part of the keypair without the public part, where this was
