OPENSSL_config.pod 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. =pod
  2. =head1 NAME
  3. OPENSSL_config, OPENSSL_no_config - simple OpenSSL configuration functions
  4. =head1 SYNOPSIS
  5. #include <openssl/conf.h>
  6. void OPENSSL_config(const char *config_name);
  7. void OPENSSL_no_config(void);
  8. =head1 DESCRIPTION
  9. OPENSSL_config() configures OpenSSL using the standard B<openssl.cnf>
  10. configuration file name using B<config_name>. If B<config_name> is NULL then
  11. the file specified in the environment variable B<OPENSSL_CONF> will be used,
  12. and if that is not set then a system default location is used.
  13. Errors are silently ignored.
  14. Multiple calls have no effect.
  15. OPENSSL_no_config() disables configuration. If called before OPENSSL_config()
  16. no configuration takes place.
  17. =head1 NOTES
  18. The OPENSSL_config() function is designed to be a very simple "call it and
  19. forget it" function.
  20. It is however B<much> better than nothing. Applications which need finer
  21. control over their configuration functionality should use the configuration
  22. functions such as CONF_modules_load() directly. This function is deprecated
  23. and its use should be avoided.
  24. Applications should instead call CONF_modules_load() during
  25. initialization (that is before starting any threads).
  26. There are several reasons why calling the OpenSSL configuration routines is
  27. advisable. For example new ENGINE functionality was added to OpenSSL 0.9.7.
  28. In OpenSSL 0.9.7 control functions can be supported by ENGINEs, this can be
  29. used (among other things) to load dynamic ENGINEs from shared libraries (DSOs).
  30. However very few applications currently support the control interface and so
  31. very few can load and use dynamic ENGINEs. Equally in future more sophisticated
  32. ENGINEs will require certain control operations to customize them. If an
  33. application calls OPENSSL_config() it doesn't need to know or care about
  34. ENGINE control operations because they can be performed by editing a
  35. configuration file.
  36. Applications should free up configuration at application closedown by calling
  37. CONF_modules_free().
  38. =head1 RETURN VALUES
  39. Neither OPENSSL_config() nor OPENSSL_no_config() return a value.
  40. =head1 SEE ALSO
  41. L<conf(5)|conf(5)>, L<CONF_load_modules_file(3)|CONF_load_modules_file(3)>,
  42. L<CONF_modules_free(3)|CONF_modules_free(3)>
  43. =head1 HISTORY
  44. OPENSSL_config() and OPENSSL_no_config() first appeared in OpenSSL 0.9.7
  45. =cut