Home
last modified time | relevance | path

Searched refs:reference (Results 1 – 25 of 119) sorted by relevance

12345

/openssl-master/doc/man3/
A DSSL_SESSION_free.pod27 SSL_SESSION_up_ref() increments the reference count on the given SSL_SESSION
30 SSL_SESSION_free() decrements the reference count of B<session> and removes
32 memory, if the reference count has reached 0.
43 object at the same time. It is therefore crucial to keep the reference
47 when an SSL_SESSION object was completely freed as the reference count
53 which the reference count was explicitly incremented (e.g.
58 incorrect reference counts and therefore program failures.
A DSSL_set_bio.pod29 ownership of one reference. Therefore, it may be necessary to increment the
49 previously set values then one reference is consumed for the rbio and one
50 reference is consumed for the wbio.
55 the same as the previously set value then one reference is consumed.
66 previously set value then one reference is consumed for the B<wbio> and no
73 were the same as each other then one reference is consumed for the B<rbio>
81 to each other, then one reference is consumed for the B<rbio> and one
82 reference is consumed for the B<wbio>.
A DENGINE_add.pod198 inherently a B<structural> reference - a structural reference is required
207 B<functional> reference. This kind of reference can be considered a
208 specialised form of structural reference, because each functional reference
211 kinds of reference independently. If you have a functional reference to an
214 until after you have released your reference.
230 the last structural reference is released.
233 structural reference will internally obtain another reference - typically
260 To obtain a functional reference from an existing structural reference,
267 implicit structural reference as well).
379 /* Release the functional reference from ENGINE_init() */
[all …]
A DX509_new.pod25 library context of I<libctx>, property query of I<propq> and a reference
35 X509_free() decrements the reference count of B<X509> structure B<a> and
36 frees it up if the reference count is zero. If B<a> is NULL nothing is done.
38 X509_up_ref() increments the reference count of B<a>.
40 X509_chain_up_ref() increases the reference count of all certificates in
49 The function X509_chain_up_ref() doesn't just up the reference count of
A DSSL_free.pod15 SSL_free() decrements the reference count of B<ssl>, and removes the SSL
17 reference count has reached 0.
29 The ssl session has reference counts from two users: the SSL object, for
30 which the reference count is removed by SSL_free() and the internal
A DSSL_CTX_sess_set_get_cb.pod61 Since sessions are reference-counted objects, the reference count on the
64 internal cache and the reference count released. If the callback returns B<1>,
65 the application retains the reference (for an entry in the
67 calling SSL_SESSION_free() when the session reference is no longer in use.
95 SSL engine to increment the reference count of the SSL_SESSION object;
96 setting B<copy> to B<0> causes the reference count to remain unchanged.
97 If the get_session_cb() does not write to B<copy>, the reference count
A DX509_cmp_time.pod27 X509_cmp_timeframe() compares the given time period with the reference time
29 B<X509_V_FLAG_USE_CHECK_TIME>; else the current time is used as reference time.
62 1 if the end time is not NULL and the reference time (which has determined as
64 reference time is before, else 0 to indicate that the reference time is in range
A DSSL_get_session.pod18 B<ssl>. The reference count of the B<SSL_SESSION> is not incremented, so
23 SSL_get1_session() is the same as SSL_get_session(), but the reference
63 reference counter is not incremented, the pointer is only valid while
70 If the data is to be kept, SSL_get1_session() will increment the reference
74 to decrement the reference count again.
78 One SSL_SESSION object, regardless of its reference count, must therefore
A DSSL_new.pod21 reference counted. Creating an B<SSL> structure for the first time increments
22 the reference count. Freeing it (using SSL_free) decrements it. When the
23 reference count drops to zero, any memory or resources allocated to the B<SSL>
26 SSL_up_ref() increments the reference count for an
36 reference count and returns the I<same> handle. It may be possible to
A DSSL_set1_host.pod29 the primary reference identifier of the peer, and should not call
32 SSL_add1_host() adds B<name> as an additional reference identifier
47 from the peer certificate that matched one of the reference
50 of the reference identifiers configured via SSL_set1_host() or
53 of the reference identifier. The returned string is allocated by
A DSSL_set_session.pod17 When the session is set, the reference count of B<session> is incremented
18 by 1. If the session is not reused, the reference count is decremented
34 One SSL_SESSION object, regardless of its reference count, must therefore
A DOSSL_PARAM_BLD.pod80 The I<bn> argument is stored by reference and the underlying BIGNUM object
89 The I<bn> argument is stored by reference and the underlying BIGNUM object
96 The string that I<buf> points to is stored by reference and must remain in
101 The memory that I<buf> points to is stored by reference and must remain in
108 The string I<buf> points to is stored by reference and must remain in
113 The memory I<buf> points to is stored by reference and must remain in
A DX509_get_pubkey.pod28 reference count incremented: this means the returned key must be freed up
30 the reference count of the returned B<EVP_PKEY> so it must not be freed up
47 return the cached structure with its reference count incremented to
A DSSL_CTX_set_cert_store.pod22 of B<ctx> to/with B<store>. The B<store>'s reference count is incremented.
50 SSL_CTX_set_cert_store() does not increment the B<store>'s reference
57 increment the reference count of the X509_STORE.
A DSSL_CTX_free.pod15 SSL_CTX_free() decrements the reference count of B<ctx>, and removes the
16 SSL_CTX object pointed to by B<ctx> and frees up the allocated memory if the reference count has re…
A DUI_create_method.pod62 This function takes a reference to a UI and starts a session, for
67 This function takes a reference to a UI and a UI String, and writes
75 This function takes a reference to a UI, and flushes everything that
82 This function takes a reference to a UI and a UI string and reads off
90 This function takes a reference to a UI, and closes the session, maybe
A DEVP_KEYEXCH_free.pod41 EVP_KEYEXCH_free() decrements the reference count for the B<EVP_KEYEXCH>
43 to EVP_KEYEXCH_fetch(). If the reference count drops to 0 then the
46 EVP_KEYEXCH_up_ref() increments the reference count for an B<EVP_KEYEXCH>
A DSSL_get_peer_certificate.pod34 The reference count of the X509 object returned by SSL_get1_peer_certificate()
39 The reference count of the X509 object returned by SSL_get0_peer_certificate()
/openssl-master/doc/internal/man3/
A Dossl_method_construct.pod64 reference counting and acts accordingly (i.e. it will call the
65 subsystem destruct() method to decrement the reference count when
101 This function is expected to increment the resulting method's reference count.
118 This function is expected to increment the I<method>'s reference count.
126 it possible for the subsystem constructor to keep a reference, which
128 If such a reference is kept, the I<provider object> reference counter
131 This function is expected to set the method's reference count to 1.
135 Decrement the I<method>'s reference count, and destruct it when
136 the reference count reaches zero.
A Dossl_provider_new.pod114 Provider objects are reference counted.
130 The provider object it finds has its reference count incremented.
136 reference count incremented.
141 The reference count of a newly created provider object will always
143 reference.
154 reference count.
157 reference count; when it drops to zero, the provider object is assumed
187 ossl_provider_free_parent() decreases the reference count on the parent
234 reference to the provider that should be used is passed back in the
253 ossl_provider_dso() returns a reference to the module, for providers
[all …]
A Dossl_cmp_ctx_set1_caPubs.pod35 The reference counts of those certificates handled successfully are increased.
51 The reference counts of those certificates handled successfully are increased.
/openssl-master/doc/man7/
A Dprovider-object.pod38 (see L</Parameter reference> below), where it's assumed to a plain UTF8 string.
45 I<By reference>
48 reference> is passed instead. It's an octet string that only the correct
56 Objects I<by reference> need a higher level of cooperation from the
67 reference>. This can only be used if the target implementation is from the
90 =head2 Parameter reference
101 =item "reference" (B<OSSL_OBJECT_PARAM_REFERENCE>) <octet string>
103 The object data I<passed by reference>.
123 object data may be I<passed by value> or I<passed by reference>.
169 item, or object data I<passed by reference>, i.e. the "reference" item).
A Dopenssl-threads.pod23 One major use of the OpenSSL thread API is to implement reference counting.
24 Many objects within OpenSSL are reference-counted, so resources are not
25 released, until the last reference is removed.
29 the reference count.
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
42 Functions that involve attributes that have reference counts themselves,
61 One example of this is the reference counting API's described above.
/openssl-master/providers/implementations/keymgmt/
A Drsa_kmgmt.c619 static void *common_load(const void *reference, size_t reference_sz, in common_load() argument
626 rsa = *(RSA **)reference; in common_load()
632 *(RSA **)reference = NULL; in common_load()
638 static void *rsa_load(const void *reference, size_t reference_sz) in rsa_load() argument
640 return common_load(reference, reference_sz, RSA_FLAG_TYPE_RSA); in rsa_load()
643 static void *rsapss_load(const void *reference, size_t reference_sz) in rsapss_load() argument
645 return common_load(reference, reference_sz, RSA_FLAG_TYPE_RSASSAPSS); in rsapss_load()
/openssl-master/crypto/engine/
A DREADME.md41 rewrites of many applications, to assume that EVP_CIPHERs can be reference
55 especially necessary considering the fact ENGINE uses reference counts to allow
94 reference) for any ENGINE that is registered to perform the algo/mode that the
103 combination represented by the provided EVP_CIPHER, then a functional reference
105 That functional reference will be stored in the context (and released on
106 cleanup) - and having that reference provides a *safe* way to use an EVP_CIPHER
112 there is no associated problem with it not having reference counts. And of
147 functional reference to the first that successfully initialised. In the latter
148 case it will also cache an extra functional reference to the ENGINE as a
155 (ie. it's simply an increment of the functional reference count, and no real
[all …]

Completed in 27 milliseconds

12345