Lines Matching +full:4 +full:- +full:data

1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "PROVIDER-OBJECT 7ossl"
58 .TH PROVIDER-OBJECT 7ossl 2025-09-30 3.5.4 OpenSSL
64 provider\-object \- A specification for a provider\-native object abstraction
73 The provider-native object abstraction is a set of \fBOSSL_PARAM\fR\|(3) keys and
74 values that can be used to pass provider-native objects to OpenSSL library
78 The intention is that certain provider-native operations can pass any sort
82 .IP 1. 4
85 This means that the \fIobject data\fR is passed as an octet string or an UTF8
89 If central OpenSSL library functionality is to handle the data directly, it
92 .IP 2. 4
95 This means that the \fIobject data\fR isn't passed directly, an \fIobject
105 .IP 1. 4
113 and possibly the \fIobject data type\fR.
115 \&\fIobject type\fR \fBOSSL_OBJECT_PKEY\fR, it will fetch a \fBprovider\-keymgmt\fR\|(7)
116 using the \fIobject data type\fR as its key type (the second argument in
118 .IP 2. 4
129 A provider-native object abstraction is an \fBOSSL_PARAM\fR\|(3) with a selection
131 .IP """data"" (\fBOSSL_OBJECT_PARAM_DATA\fR) <octet string> or <UTF8 string>" 4
132 .IX Item """data"" (OSSL_OBJECT_PARAM_DATA) <octet string> or <UTF8 string>"
133 The object data \fIpassed by value\fR.
134 .IP """reference"" (\fBOSSL_OBJECT_PARAM_REFERENCE\fR) <octet string>" 4
136 The object data \fIpassed by reference\fR.
137 .IP """type"" (\fBOSSL_OBJECT_PARAM_TYPE\fR) <integer>" 4
141 .RS 4
142 .IP \fBOSSL_OBJECT_NAME\fR 4
144 The object data may only be \fIpassed by value\fR, and should be a UTF8
147 This is useful for \fBprovider\-storemgmt\fR\|(7) when a URI load results in new
149 .IP \fBOSSL_OBJECT_PKEY\fR 4
151 The object data is suitable as provider-native \fBEVP_PKEY\fR key data.  The
152 object data may be \fIpassed by value\fR or \fIpassed by reference\fR.
153 .IP \fBOSSL_OBJECT_CERT\fR 4
155 The object data is suitable as \fBX509\fR data.  The object data for this
158 Since there's no provider-native X.509 object, OpenSSL libraries that
159 receive this object abstraction are expected to convert the data to a
161 .IP \fBOSSL_OBJECT_CRL\fR 4
163 The object data is suitable as \fBX509_CRL\fR data.  The object data can
166 Since there's no provider-native X.509 CRL object, OpenSSL libraries that
167 receive this object abstraction are expected to convert the data to a
170 .RS 4
172 .IP """data-type"" (\fBOSSL_OBJECT_PARAM_DATA_TYPE\fR) <UTF8 string>" 4
173 .IX Item """data-type"" (OSSL_OBJECT_PARAM_DATA_TYPE) <UTF8 string>"
175 object type; if it is \fBOSSL_OBJECT_PKEY\fR, the data type is expected to be a
176 key type suitable for fetching a \fBprovider\-keymgmt\fR\|(7) that can handle the
177 data.
178 .IP """data-structure"" (\fBOSSL_OBJECT_PARAM_DATA_STRUCTURE\fR) <UTF8 string>" 4
179 .IX Item """data-structure"" (OSSL_OBJECT_PARAM_DATA_STRUCTURE) <UTF8 string>"
182 .IP """desc"" (\fBOSSL_OBJECT_PARAM_DESC\fR) <UTF8 string>" 4
186 When a provider-native object abstraction is used, it \fImust\fR contain object
187 data in at least one form (object data \fIpassed by value\fR, i.e. the "data"
188 item, or object data \fIpassed by reference\fR, i.e. the "reference" item).
203 Copyright 2020\-2022 The OpenSSL Project Authors. All Rights Reserved.