Lines Matching refs:public
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
72 and verifying normally requires the presence of a public key.
74 =for comment ED signature require both the private and public key...
77 producing signatures, although not being public key algorithms; "POLY1305",
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
100 should be appropriate for the type of the key. The public key data will be
108 indicates what kind of key this is. The value should be a NID for a public key
113 be used with most MACs implemented as public key algorithms, so key types such
120 public key data. The B<EVP_PKEY> structure will be initialised without any
121 private key information. Algorithm types that support raw public keys are
125 EVP_PKEY_new_raw_private_key() except that I<key> points to the raw public key
127 information. Algorithm types that support raw public keys are
144 public key data. The size of the I<pub> buffer should be in I<*len> on entry
148 responsible for ensuring that the buffer is large enough to receive the public
149 key data. This function only works for algorithms that support raw public keys.
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