SSL_CTX_set_client_cert_cb.pod 4.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394
  1. =pod
  2. =head1 NAME
  3. SSL_CTX_set_client_cert_cb, SSL_CTX_get_client_cert_cb - handle client certificate callback function
  4. =head1 SYNOPSIS
  5. #include <openssl/ssl.h>
  6. void SSL_CTX_set_client_cert_cb(SSL_CTX *ctx, int (*client_cert_cb)(SSL *ssl, X509 **x509, EVP_PKEY **pkey));
  7. int (*SSL_CTX_get_client_cert_cb(SSL_CTX *ctx))(SSL *ssl, X509 **x509, EVP_PKEY **pkey);
  8. int (*client_cert_cb)(SSL *ssl, X509 **x509, EVP_PKEY **pkey);
  9. =head1 DESCRIPTION
  10. SSL_CTX_set_client_cert_cb() sets the B<client_cert_cb()> callback, that is
  11. called when a client certificate is requested by a server and no certificate
  12. was yet set for the SSL object.
  13. When B<client_cert_cb()> is NULL, no callback function is used.
  14. SSL_CTX_get_client_cert_cb() returns a pointer to the currently set callback
  15. function.
  16. client_cert_cb() is the application defined callback. If it wants to
  17. set a certificate, a certificate/private key combination must be set
  18. using the B<x509> and B<pkey> arguments and "1" must be returned. The
  19. certificate will be installed into B<ssl>, see the NOTES and BUGS sections.
  20. If no certificate should be set, "0" has to be returned and no certificate
  21. will be sent. A negative return value will suspend the handshake and the
  22. handshake function will return immediately. L<SSL_get_error(3)|SSL_get_error(3)>
  23. will return SSL_ERROR_WANT_X509_LOOKUP to indicate, that the handshake was
  24. suspended. The next call to the handshake function will again lead to the call
  25. of client_cert_cb(). It is the job of the client_cert_cb() to store information
  26. about the state of the last call, if required to continue.
  27. =head1 NOTES
  28. During a handshake (or renegotiation) a server may request a certificate
  29. from the client. A client certificate must only be sent, when the server
  30. did send the request.
  31. When a certificate was set using the
  32. L<SSL_CTX_use_certificate(3)|SSL_CTX_use_certificate(3)> family of functions,
  33. it will be sent to the server. The TLS standard requires that only a
  34. certificate is sent, if it matches the list of acceptable CAs sent by the
  35. server. This constraint is violated by the default behavior of the OpenSSL
  36. library. Using the callback function it is possible to implement a proper
  37. selection routine or to allow a user interaction to choose the certificate to
  38. be sent.
  39. If a callback function is defined and no certificate was yet defined for the
  40. SSL object, the callback function will be called.
  41. If the callback function returns a certificate, the OpenSSL library
  42. will try to load the private key and certificate data into the SSL
  43. object using the SSL_use_certificate() and SSL_use_private_key() functions.
  44. Thus it will permanently install the certificate and key for this SSL
  45. object. It will not be reset by calling L<SSL_clear(3)|SSL_clear(3)>.
  46. If the callback returns no certificate, the OpenSSL library will not send
  47. a certificate.
  48. =head1 BUGS
  49. The client_cert_cb() cannot return a complete certificate chain, it can
  50. only return one client certificate. If the chain only has a length of 2,
  51. the root CA certificate may be omitted according to the TLS standard and
  52. thus a standard conforming answer can be sent to the server. For a
  53. longer chain, the client must send the complete chain (with the option
  54. to leave out the root CA certificate). This can only be accomplished by
  55. either adding the intermediate CA certificates into the trusted
  56. certificate store for the SSL_CTX object (resulting in having to add
  57. CA certificates that otherwise maybe would not be trusted), or by adding
  58. the chain certificates using the
  59. L<SSL_CTX_add_extra_chain_cert(3)|SSL_CTX_add_extra_chain_cert(3)>
  60. function, which is only available for the SSL_CTX object as a whole and that
  61. therefore probably can only apply for one client certificate, making
  62. the concept of the callback function (to allow the choice from several
  63. certificates) questionable.
  64. Once the SSL object has been used in conjunction with the callback function,
  65. the certificate will be set for the SSL object and will not be cleared
  66. even when L<SSL_clear(3)|SSL_clear(3)> is being called. It is therefore
  67. mandatory to destroy the SSL object using L<SSL_free(3)|SSL_free(3)>
  68. and create a new one to return to the previous state.
  69. =head1 SEE ALSO
  70. L<ssl(3)|ssl(3)>, L<SSL_CTX_use_certificate(3)|SSL_CTX_use_certificate(3)>,
  71. L<SSL_CTX_add_extra_chain_cert(3)|SSL_CTX_add_extra_chain_cert(3)>,
  72. L<SSL_get_client_CA_list(3)|SSL_get_client_CA_list(3)>,
  73. L<SSL_clear(3)|SSL_clear(3)>, L<SSL_free(3)|SSL_free(3)>
  74. =cut