Lines Matching full:an

50 object (I<obj_raw>) or an object abstraction (I<object_abstract>, see
51 L<provider-object(7)>) into an encoded form, and write the result to
60 passed from one to the next.  For example, there may be an
61 implementation to encode an object to DER (that object is assumed to
93 function pointer from an L<OSSL_DISPATCH(3)> element named
126 The name of an implementation should match the type of object it handles.
127 For example, an implementation that encodes an RSA key should be named "RSA".
128 Likewise, an implementation that further encodes DER should be named "DER".
130 Properties can be used to further specify details about an implementation:
147 An implementation with that output type outputs human readable text, making
153 An implementation with that output type outputs PEM formatted data.
157 An implementation with that output type outputs DER formatted data.
161 An implementation with that output type outputs MSBLOB formatted data.
165 An implementation with that output type outputs PVK formatted data.
172 object.  An example could be C<pkcs8>, to specify explicitly that an object
173 (presumably an asymmetric key pair, in this case) will be wrapped in a
186 Sometimes, an object has more than one subset of data that is interesting to
188 be encoded, with a set of bits I<selection> that are passed in an B<int>.
193 the object is an asymmetric keypair.
242 I<obj_raw>) or an object abstraction (in I<obj_abstract>), and should output
245 The encoding functions also take an L<OSSL_PASSPHRASE_CALLBACK(3)> function
265 should return an error.
276 property strings return an error on receiving this parameter unless
282 It currently has an effect only on DSA keys.
304 parameter was invalid or caused an error, for which 0 is returned.
306 OSSL_FUNC_encoder_settable_ctx_params() returns a pointer to an array of