From eb9264fc2ef786e8c4e3d430834b9b9e9e0b9c0a Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Mon, 9 Oct 2006 16:00:16 +0000 Subject: OpenSSL 0.9.8d base code import svn path=/openssl/vendor/0.9.8d/CHANGES; revision=373 --- openssl/vendor/0.9.8d/doc/ssl/SSL_SESSION_free.pod | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 openssl/vendor/0.9.8d/doc/ssl/SSL_SESSION_free.pod (limited to 'openssl/vendor/0.9.8d/doc/ssl/SSL_SESSION_free.pod') diff --git a/openssl/vendor/0.9.8d/doc/ssl/SSL_SESSION_free.pod b/openssl/vendor/0.9.8d/doc/ssl/SSL_SESSION_free.pod new file mode 100644 index 00000000..558de01d --- /dev/null +++ b/openssl/vendor/0.9.8d/doc/ssl/SSL_SESSION_free.pod @@ -0,0 +1,55 @@ +=pod + +=head1 NAME + +SSL_SESSION_free - free an allocated SSL_SESSION structure + +=head1 SYNOPSIS + + #include + + void SSL_SESSION_free(SSL_SESSION *session); + +=head1 DESCRIPTION + +SSL_SESSION_free() decrements the reference count of B and removes +the B structure pointed to by B and frees up the allocated +memory, if the the reference count has reached 0. + +=head1 NOTES + +SSL_SESSION objects are allocated, when a TLS/SSL handshake operation +is successfully completed. Depending on the settings, see +L, +the SSL_SESSION objects are internally referenced by the SSL_CTX and +linked into its session cache. SSL objects may be using the SSL_SESSION object; +as a session may be reused, several SSL objects may be using one SSL_SESSION +object at the same time. It is therefore crucial to keep the reference +count (usage information) correct and not delete a SSL_SESSION object +that is still used, as this may lead to program failures due to +dangling pointers. These failures may also appear delayed, e.g. +when an SSL_SESSION object was completely freed as the reference count +incorrectly became 0, but it is still referenced in the internal +session cache and the cache list is processed during a +L operation. + +SSL_SESSION_free() must only be called for SSL_SESSION objects, for +which the reference count was explicitly incremented (e.g. +by calling SSL_get1_session(), see L) +or when the SSL_SESSION object was generated outside a TLS handshake +operation, e.g. by using L. +It must not be called on other SSL_SESSION objects, as this would cause +incorrect reference counts and therefore program failures. + +=head1 RETURN VALUES + +SSL_SESSION_free() does not provide diagnostic information. + +=head1 SEE ALSO + +L, L, +L, +L, + L + +=cut -- cgit v1.2.3