SSL_CTX_set_client_cert_cb.pod 4.7 KB

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