Lines Matching full:implementation

193 The \s-1ENCODER\s0 implementation may be part of a chain, where data is
195 implementation to encode an object to \s-1DER\s0 (that object is assumed to
253 The name of an implementation should match the type of object it handles.
254 For example, an implementation that encodes an \s-1RSA\s0 key should be named \*(L"\s-1RSA\*(R".\s0
255 Likewise, an implementation that further encodes \s-1DER\s0 should be named \*(L"\s-1DER\*(R".\s0
257 Properties can be used to further specify details about an implementation:
260 This property is used to specify what type of output the implementation
269 An implementation with that output type outputs human readable text, making
270 that implementation suitable for \f(CW\*(C`\-text\*(C'\fR output in diverse \fBopenssl\fR\|(1)
274 An implementation with that output type outputs \s-1PEM\s0 formatted data.
277 An implementation with that output type outputs \s-1DER\s0 formatted data.
280 An implementation with that output type outputs \s-1MSBLOB\s0 formatted data.
283 An implementation with that output type outputs \s-1PVK\s0 formatted data.
315 \&\fBOSSL_FUNC_encoder_does_selection()\fR should tell if a particular implementation
339 therefore be unsuitable for direct use with a given \s-1ENCODER\s0 implementation.
340 Provided that the foreign provider's implementation to handle the object has
342 implementation should be able to import that array and create a suitable
371 If this name is invalid for the encoding implementation, the
372 implementation should refuse to perform the encoding, i.e.
383 The encoding implementation isn't obligated to use this value.
411 \&\fBOSSL_FUNC_encoder_does_selection()\fR returns 1 if the encoder implementation