Lines Matching full:object

133 .IX Title "PROVIDER-OBJECT 7ossl"
134 .TH PROVIDER-OBJECT 7ossl "2023-09-19" "3.0.11" "OpenSSL"
140 provider\-object \- A specification for a provider\-native object abstraction
149 The provider-native object abstraction is a set of \s-1\fBOSSL_PARAM\s0\fR\|(3) keys and
155 of object that belong with other operations, or with OpenSSL library code.
157 An object may be passed in the following manners:
161 This means that the \fIobject data\fR is passed as an octet string or an \s-1UTF8\s0
163 The encoding of the object depends on the context it's used in; for example,
166 \&\fBmust\fR be encoded in \s-1DER\s0 for all object types except for \fB\s-1OSSL_OBJECT_NAME\s0\fR
171 This means that the \fIobject data\fR isn't passed directly, an \fIobject
179 implementation where the object originated (let's call it X) and its target
182 \&\fIAn object loading function in the target implementation\fR
184 The target implementation (Y) may have a function that can take an \fIobject
186 same provider as the one originating the object abstraction in question (X).
188 The exact target implementation to use is determined from the \fIobject type\fR
189 and possibly the \fIobject data type\fR.
190 For example, when the OpenSSL library receives an object abstraction with the
192 using the \fIobject data type\fR as its key type (the second argument in
195 \&\fIAn object exporter in the originating implementation\fR
198 exporter function can be used to export the object in \s-1\fBOSSL_PARAM\s0\fR\|(3) form,
205 A provider-native object abstraction is an \s-1\fBOSSL_PARAM\s0\fR\|(3) with a selection
210 The object data \fIpassed by value\fR.
214 The object data \fIpassed by reference\fR.
218 The \fIobject type\fR, a number that may have any of the following values (all
223 The object data may only be \fIpassed by value\fR, and should be a \s-1UTF8\s0
230 The object data is suitable as provider-native \fB\s-1EVP_PKEY\s0\fR key data.  The
231 object data may be \fIpassed by value\fR or \fIpassed by reference\fR.
234 The object data is suitable as \fBX509\fR data.  The object data for this
235 object type can only be \fIpassed by value\fR, and should be an octet string.
237 Since there's no provider-native X.509 object, OpenSSL libraries that
238 receive this object abstraction are expected to convert the data to a
239 \&\fBX509\fR object with \fBd2i_X509()\fR.
242 The object data is suitable as \fBX509_CRL\fR data.  The object data can
245 Since there's no provider-native X.509 \s-1CRL\s0 object, OpenSSL libraries that
246 receive this object abstraction are expected to convert the data to a
247 \&\fBX509_CRL\fR object with \fBd2i_X509_CRL()\fR.
254 The specific type of the object content.  Legitimate values depend on the
255 object type; if it is \fB\s-1OSSL_OBJECT_PKEY\s0\fR, the data type is expected to be a
261 The outermost structure of the object content.  Legitimate values depend on
262 the object type.
266 A human readable text that describes extra details on the object.
268 When a provider-native object abstraction is used, it \fImust\fR contain object
269 data in at least one form (object data \fIpassed by value\fR, i.e. the \*(L"data\*(R"
270 item, or object data \fIpassed by reference\fR, i.e. the \*(L"reference\*(R" item).
274 For objects with the object type \fB\s-1OSSL_OBJECT_NAME\s0\fR, that object type