Home
last modified time | relevance | path

Searched refs:object (Results 1 – 25 of 267) sorted by relevance

1234567891011

/openssl-master/doc/man7/
A Dprovider-object.pod5 provider-object - A specification for a provider-native object abstraction
47 This means that the I<object data> isn't passed directly, an I<object
71 and possibly the I<object data type>.
99 The object data I<passed by value>.
103 The object data I<passed by reference>.
127 The object data is suitable as B<X509> data. The object data for this
132 B<X509> object with d2i_X509().
136 The object data is suitable as B<X509_CRL> data. The object data can
159 the object type.
167 When a provider-native object abtraction is used, it I<must> contain object
[all …]
A Dopenssl-threads.pod10 object or function can be used by multiple threads at the same time.
27 certificate object is added into an B<X509_STORE> trust store).
30 Failure to match B<I<object>_up_ref>() calls with the right number of
34 Many objects have set and get API's to set attributes in the object.
35 A C<set0> passes ownership from the caller to the object and a
37 remains with the object and a reference to it is returned.
39 updates the attribute's reference count so that the object is shared
40 between the caller and the object; the caller must free the returned
51 as long as the API's being invoked don't modify the object; in this
59 Another instance of thread-safety is when updates to an object's
[all …]
A Dprovider-encoder.pod30 /* 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
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
172 object. An example could be C<pkcs8>, to specify explicitly that an object
193 the object is an asymmetric keypair.
198 match the original object that was encoded.
230 object to be passed to OSSL_FUNC_encoder_encode()'s I<obj_raw>.
[all …]
A Dprovider-keymgmt.pod17 /* Key object (keydata) creation and destruction */
31 /* Key loading by object reference, also a constructor */
34 /* Key object information */
40 /* Key object content checks */
48 /* Key object import and export functions */
55 /* Key object duplication, a constructor */
58 /* Key object validation */
214 key object, but that is not mandatory.
221 more elaborate context based key object constructor.
225 of contents the key object to be generated should get.
[all …]
A Dprovider-decoder.pod30 /* Functions to decode object data */
36 /* Functions to export a decoded object */
49 object reference or intermediate decoded data from an encoded form
52 data or object reference is passed along with eventual metadata
61 implementation to decode an object from PEM to DER, and another one
62 that decodes DER to a provider-native object.
65 a provider-native object referenced by an object reference. To import
108 The name of an implementation should match the target type of object
217 supports the type of the object and provides an import function.
226 the B<OSSL_CORE_BIO> I<in> to produce decoded data or an object to be
[all …]
A Dprovider-storemgmt.pod37 to the OpenSSL library in provider-native object abstraction form (see
38 L<provider-object(7)>). The OpenSSL library is then responsible for
94 OSSL_FUNC_store_load() loads the next object from the URI opened by
95 OSSL_FUNC_store_open(), creates an object abstraction for it (see
96 L<provider-object(7)>), and calls I<object_cb> with it as well as
116 object types match the expectation too.
125 Indicates that the caller wants to search for an object with the given
133 Indicates that the caller wants to search for an object with the given
141 Indicates that the caller wants to search for an object with the given
148 Indicates that the caller wants to search for an object with the given
[all …]
/openssl-master/apps/lib/
A Dapp_x509.c37 static int x509_ctrl(void *object, int cmd, void *value, size_t value_n) in x509_ctrl() argument
51 X509_set0_distinguishing_id(object, v); in x509_ctrl()
61 static int x509_req_ctrl(void *object, int cmd, void *value, size_t value_n) in x509_req_ctrl() argument
75 X509_REQ_set0_distinguishing_id(object, v); in x509_req_ctrl()
85 static int do_x509_ctrl_string(int (*ctrl)(void *object, int cmd, in do_x509_ctrl_string() argument
87 void *object, const char *value) in do_x509_ctrl_string()
123 rv = ctrl(object, cmd, vtmp, vtmp_len); in do_x509_ctrl_string()
/openssl-master/doc/man3/
A Dd2i_SSL_SESSION.pod5 d2i_SSL_SESSION, i2d_SSL_SESSION - convert SSL_SESSION object from/to ASN1 representation
17 These functions decode and encode an SSL_SESSION object.
21 list, when being inserted into one SSL_CTX object's session cache.
22 One SSL_SESSION object, regardless of its reference count, must therefore
23 only be used with one SSL_CTX object (and the SSL objects created
24 from this SSL_CTX object).
29 object. In case of failure the NULL-pointer is returned and the error message
A DOSSL_STORE_INFO.pod67 Supported OpenSSL type object can be extracted using one of
73 same object with its reference count increased), which can be used
82 type number for the object inside.
91 all take a B<OSSL_STORE_INFO> and return the object it holds if the
99 all take a B<OSSL_STORE_INFO> and return a duplicate the object it
108 create a B<OSSL_STORE_INFO> object to hold the given input object.
109 On success the input object is consumed.
132 Currently supported object types are:
145 of object URIs.
194 a pointer to the OpenSSL object on success, NULL otherwise.
[all …]
A DDSA_get0_pqg.pod10 setting data in a DSA object
41 A DSA object contains the parameters B<p>, B<q> and B<g>. It also contains a
52 this function transfers the memory management of the values to the DSA object,
65 object. The private key may be NULL. On subsequent calls, either may be NULL,
68 object, and therefore they should not be freed directly after this function has
75 DSA_set_flags() sets the flags in the B<flags> parameter on the DSA object.
78 passed in the B<flags> parameter are currently set in the DSA object. Multiple
81 within the DSA object.
84 object, or NULL if no such ENGINE has been set.
88 Values retrieved with DSA_get0_key() are owned by the DSA object used
[all …]
A DSSL_CTX_set_ssl_version.pod20 SSL_CTX object is retained, with the exception of the configured TLS ciphers,
26 object. It may be reset, when SSL_clear() is called.
37 an SSL object, the method of the SSL object is reset to the method currently
38 set in the corresponding SSL_CTX object.
41 it would usually be preferable to create a new SSL_CTX object than to
A DSSL_get_session.pod35 SSL_SESSION object but that object cannot be used for resuming the session. See
37 SSL_SESSION object can be used for resumption or not.
46 The preferred way for applications to obtain a resumable SSL_SESSION object is
50 SSL_SESSION object that cannot be used for resumption in TLSv1.3. It also
59 In TLSv1.3 it is recommended that each SSL_SESSION object is only used for
77 list, when being inserted into one SSL_CTX object's session cache.
78 One SSL_SESSION object, regardless of its reference count, must therefore
79 only be used with one SSL_CTX object (and the SSL objects created
80 from this SSL_CTX object).
A DRSA_get0_key.pod13 - Routines for getting and setting data in an RSA object
59 An RSA object contains the components for the public and private key,
69 'triplet' in an RSA object. A triplet contains three members, B<r>, B<d>
83 the first time this function is called on a given RSA object. The
87 the RSA object, and therefore the values that have been passed in
103 into an RSA object.
116 set in the RSA object. Multiple flags can be tested in one go. All
119 RSA object.
122 this RSA object, or NULL if no such ENGINE has been set.
124 RSA_get_version() returns the version of an RSA object B<r>.
[all …]
A DOBJ_nid2obj.pod9 - ASN1 object utility functions
48 The ASN1 object utility functions process ASN1_OBJECT structures which are
66 a long name, a short name or the numerical representation of an object.
87 OBJ_create() adds a new object to the internal table. I<oid> is the
88 numerical form of the object, I<sn> the short name and I<ln> the
89 long name. A new NID is returned for the created object in case of
125 is only a single constant structure for each table object.
160 Create an object for B<commonName>:
164 Check if an object is B<commonName>
169 Create a new NID and initialize an object from it:
[all …]
A DSSL_CTX_set_client_cert_cb.pod21 was yet set for the SSL object.
56 SSL object, the callback function will be called.
59 object using the SSL_use_certificate() and SSL_use_private_key() functions.
61 object. It will not be reset by calling L<SSL_clear(3)>.
79 certificate store for the SSL_CTX object (resulting in having to add
83 function, which is only available for the SSL_CTX object as a whole and that
88 Once the SSL object has been used in conjunction with the callback function,
89 the certificate will be set for the SSL object and will not be cleared
91 mandatory to destroy the SSL object using L<SSL_free(3)>
A DSSL_clear.pod5 SSL_clear - reset SSL object to allow another connection
20 SSL_clear is used to prepare an SSL object for a new connection. While all
28 If a session was closed cleanly, the session object will be kept and all
31 session was a TLSv1 session, a SSL client object will use a TLSv1 client
32 method for the next handshake and a SSL server object will use a TLSv1
39 SSL_clear() resets the SSL object to allow for another connection. The
A DPKCS12_SAFEBAG_get1_cert.pod38 PKCS12_SAFEBAG_get_bag_nid() gets the type of the object contained within the
42 PKCS12_SAFEBAG_get0_bag_obj() retrieves the object contained within the safeBag.
47 PKCS12_SAFEBAG_get0_p8inf() and PKCS12_SAFEBAG_get0_pkcs8() return the PKCS8 object
56 or bag object, or -1 if there is no corresponding NID.
57 Other functions return a valid object of the specified type or NULL if an error occurred.
A DX509_dup.pod304 - ASN1 object utilities
338 Every ASN1 object as a global variable, TYPE_it, that describes the item
350 B<I<TYPE>_new>() allocates an empty object of the indicated type.
351 The object returned must be released by calling B<I<TYPE>_free>().
355 algorithms from providers. This created object can then be used when loading
358 B<I<TYPE>_dup>() copies an existing object, leaving it untouched.
360 B<I<TYPE>_free>() releases the object and all pointers and sub-objects
363 B<I<TYPE>_print_ctx>() prints the object I<a> on the specified BIO I<out>.
372 the object or NULL on failure.
A DDH_get0_pqg.pod9 DH_get_length, DH_set_length - Routines for getting and setting data in a DH object
45 A DH object contains the parameters I<p>, I<q> and I<g>. Note that the I<q>
59 this function transfers the memory management of the values to the DH object,
80 of the key values to the DH object, and therefore they should not be freed
87 DH_set_flags() sets the flags in the I<flags> parameter on the DH object.
90 passed in the I<flags> parameter are currently set in the DH object. Multiple
93 within the DH object.
100 length parameter associated with this DH object. If the length is nonzero then
111 Values retrieved with DH_get0_key() are owned by the DH object used
123 DH_test_flags() returns the current state of the flags in the DH object.
[all …]
A DEC_KEY_new.pod106 Calling EC_KEY_free() decrements the reference count for the EC_KEY object,
112 EC_KEY_dup() creates a new EC_KEY object and copies I<ec_key> into it.
115 object.
118 this EC_KEY object.
121 I<eckey> object. I<eckey> must have an EC_GROUP object associated with it
127 EC_KEY_check_key() performs various sanity checks on the EC_KEY object to
131 on its affine co-ordinates; i.e., it constructs an EC_POINT object based on
146 object. Any flags that are already set are left set. The flags currently
153 EC_KEY_set_asn1_flag() sets the asn1_flag on the underlying EC_GROUP object
191 created EC_KEY object, or NULL on error.
[all …]
A DASN1_item_sign.pod42 ASN1_item_sign_ex() is used to sign arbitrary ASN1 data using a data object
44 The data that is signed is formed by taking the data object in I<data> and
70 The data that is verified is formed by taking the data object in I<data> and
95 In the following example a 'MyObject' object is signed using the key contained
96 in an EVP_MD_CTX. The signature is written to MyObject.signature. The object is
102 /* An object used to store the ASN1 data fields that will be signed */
111 * A higher level object containing the ASN1 fields, signature alg and
166 * it contains the mapping between ASN.1 data and an object MySignInfoObject
167 * obj->info is the 'MySignInfoObject' object that will be
191 /* Load the der data back into an object */
[all …]
/openssl-master/doc/internal/man3/
A Dossl_rsa_get0_all_params.pod6 - Internal routines for getting and setting data in an RSA object
22 in the B<RSA> object I<r> to the contents of the stacks of BIGNUMs I<primes>,
23 I<exps> and I<coeffs>. The B<RSA> object takes ownership of the BIGNUMs,
27 in the B<RSA> object I<r> and pushes them on the stacks of constant BIGNUMs
28 I<primes>, I<exps> and I<coeffs>. The B<RSA> object retains ownership of the
40 if the B<RSA> object is a multi-prime RSA key.
45 if the B<RSA> object is a multi-prime RSA key.
50 if the B<RSA> object is a multi-prime RSA key.
/openssl-master/include/internal/
A Drefcount.h173 # define REF_PRINT_EX(text, count, object) \ argument
174 OSSL_TRACE3(REF_COUNT, "%p:%4d:%s\n", (object), (count), (text));
175 # define REF_PRINT_COUNT(text, object) \ argument
176 REF_PRINT_EX(text, object->references, (void *)object)
/openssl-master/crypto/x509/
A Dx509_v3.c52 if (OBJ_cmp(ex->object, obj) == 0) in X509v3_get_ext_by_OBJ()
188 ASN1_OBJECT_free(ex->object); in X509_EXTENSION_set_object()
189 ex->object = OBJ_dup(obj); in X509_EXTENSION_set_object()
190 return ex->object != NULL; in X509_EXTENSION_set_object()
217 return ex->object; in X509_EXTENSION_get_object()
/openssl-master/doc/man1/
A Dopenssl-format-options.pod76 A DER-encoded file containing a PKCS#12 object.
87 ----- BEGIN object-type -----
91 ----- END object-type -----
94 The I<object-type> must match the type of object that is expected.
120 The following legacy I<object-type>'s are also supported for compatibility
130 An S/MIME object as described in IETF RFC 8551.

Completed in 27 milliseconds

1234567891011