Lines Matching refs:object
30 /* Functions to encode object data */
38 /* Functions to import and free a temporary object to be encoded */
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
61 implementation to encode an object to DER (that object is assumed to
71 L<provider-object(7)> already defines a way to pass such data,
81 The encoding using a provider side object can only be safely used
126 The name of an implementation should match the type of object it handles.
172 object. An example could be C<pkcs8>, to specify explicitly that an object
186 Sometimes, an object has more than one subset of data that is interesting to
190 This set of bits depend entirely on what kind of provider-side object is
193 the object is an asymmetric keypair.
197 and if there's a corresponding decoder, the resulting decoded object must
198 match the original object that was encoded.
225 A provider-native object may be associated with a foreign provider, and may
227 Provided that the foreign provider's implementation to handle the object has
228 a function to export that object in L<OSSL_PARAM(3)> array form, the ENCODER
230 object to be passed to OSSL_FUNC_encoder_encode()'s I<obj_raw>.
233 given with I<selection> to create a provider-native object that can be
236 OSSL_FUNC_encoder_free_object() should free the object that was created with
241 OSSL_FUNC_encoder_encode() should take a provider-native object (in
242 I<obj_raw>) or an object abstraction (in I<obj_abstract>), and should output
243 the object in encoded form to the B<OSSL_CORE_BIO>. The I<selection> bits,
294 of object it's being prompted for.
