SSL_new.pod 2.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283
  1. =pod
  2. =head1 NAME
  3. SSL_dup, SSL_new, SSL_up_ref - create an SSL structure for a connection
  4. =head1 SYNOPSIS
  5. #include <openssl/ssl.h>
  6. SSL *SSL_dup(SSL *s);
  7. SSL *SSL_new(SSL_CTX *ctx);
  8. int SSL_up_ref(SSL *s);
  9. =head1 DESCRIPTION
  10. SSL_new() creates a new B<SSL> structure which is needed to hold the
  11. data for a TLS/SSL connection. The new structure inherits the settings
  12. of the underlying context B<ctx>: connection method,
  13. options, verification settings, timeout settings. An B<SSL> structure is
  14. reference counted. Creating an B<SSL> structure for the first time increments
  15. the reference count. Freeing it (using SSL_free) decrements it. When the
  16. reference count drops to zero, any memory or resources allocated to the B<SSL>
  17. structure are freed.
  18. SSL_up_ref() increments the reference count for an
  19. existing B<SSL> structure.
  20. SSL_dup() duplicates an existing B<SSL> structure into a new allocated one
  21. or just increments the reference count if the connection is active. All
  22. settings are inherited from the original B<SSL> structure. Dynamic data (i.e.
  23. existing connection details) are not copied, the new B<SSL> is set into an
  24. initial accept (server) or connect (client) state.
  25. SSL_dup() allows applications to configure an SSL handle for use in multiple
  26. SSL connections, and then duplicate it prior to initiating each connection
  27. with the duplicated handle. Use of SSL_dup() avoids the need to repeat
  28. the configuration of the handles for each connection.
  29. For SSL_dup() to work, the connection MUST be in its initial state and
  30. MUST NOT have not yet have started the SSL handshake. For connections
  31. that are not in their initial state SSL_dup() just increments an internal
  32. reference count and returns the I<same> handle. It may be possible to
  33. use L<SSL_clear(3)> to recycle an SSL handle that is not in its initial
  34. state for re-use, but this is best avoided. Instead, save and restore
  35. the session, if desired, and construct a fresh handle for each connection.
  36. =head1 RETURN VALUES
  37. The following return values can occur:
  38. =over 4
  39. =item NULL
  40. The creation of a new SSL structure failed. Check the error stack to
  41. find out the reason.
  42. =item Pointer to an SSL structure
  43. The return value points to an allocated SSL structure.
  44. SSL_up_ref() returns 1 for success and 0 for failure.
  45. =back
  46. =head1 SEE ALSO
  47. L<SSL_free(3)>, L<SSL_clear(3)>,
  48. L<SSL_CTX_set_options(3)>,
  49. L<SSL_get_SSL_CTX(3)>,
  50. L<ssl(7)>
  51. =head1 COPYRIGHT
  52. Copyright 2000-2017 The OpenSSL Project Authors. All Rights Reserved.
  53. Licensed under the Apache License 2.0 (the "License"). You may not use
  54. this file except in compliance with the License. You can obtain a copy
  55. in the file LICENSE in the source distribution or at
  56. L<https://www.openssl.org/source/license.html>.
  57. =cut