Lines Matching refs:to
21 /* Functions to construct / destruct / manipulate the encoder context */
27 /* Functions to check selection support */
30 /* Functions to encode object data */
38 /* Functions to import and free a temporary object to be encoded */
47 not limited to serialization.>
49 The ENCODER operation is a generic method to encode a provider-native
51 L<provider-object(7)>) into an encoded form, and write the result to
52 the given OSSL_CORE_BIO. If the caller wants to get the encoded
53 stream to memory, it should provide a L<BIO_s_mem(3)> B<BIO>.
55 The encoder doesn't need to know more about the B<OSSL_CORE_BIO>
56 pointer than being able to pass it to the appropriate BIO upcalls (see
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
63 that encodes DER to PEM (that one would receive the DER encoding via
70 original data type, that need to be passed alongside it, and since
71 L<provider-object(7)> already defines a way to pass such data,
72 inventing another way to do it makes things even more complicated.
77 encoder to be used for data that's been exported from another
78 provider, and thereby allow them to exist independently of each
92 named B<OSSL_FUNC_{name}_fn>, and a helper function to retrieve the
130 Properties can be used to further specify details about an implementation:
136 This property is used to specify what type of output the implementation
171 This property is used to specify the structure that is used for the encoded
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
187 treat separately or together. It's possible to specify what subsets are to
191 passed. For example, those bits are assumed to be the same as those used
195 ENCODER implementations are free to regard the I<selection> as a set of
205 OSSL_FUNC_encoder_newctx() returns a context to be used with the rest of
211 OSSL_FUNC_encoder_set_ctx_params() sets context data according to parameters
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
229 implementation should be able to import that array and create a suitable
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
234 passed as I<obj_raw> to OSSL_FUNC_encoder_encode().
243 the object in encoded form to the B<OSSL_CORE_BIO>. The I<selection> bits,
246 pointer along with a pointer to application data I<cbarg>, which should be
258 The name of the encryption cipher to be used when generating encrypted
263 implementation should refuse to perform the encoding, i.e.
269 The properties to be queried when trying to fetch the algorithm given
271 This must be given together with the "cipher" parameter to be
274 The encoding implementation isn't obligated to use this value.
281 If set to 0 disables saving of key domain parameters. Default is 1.
293 prompt. This could be used to give the user information on what kind
300 OSSL_FUNC_encoder_newctx() returns a pointer to a context, or NULL on
306 OSSL_FUNC_encoder_settable_ctx_params() returns a pointer to an array of
