README 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. Configuration modules. These are a set of modules which can perform
  2. various configuration functions.
  3. Currently the routines should be called at most once when an application
  4. starts up: that is before it starts any threads.
  5. The routines read a configuration file set up like this:
  6. -----
  7. #default section
  8. openssl_conf=init_section
  9. [init_section]
  10. module1=value1
  11. #Second instance of module1
  12. module1.1=valueX
  13. module2=value2
  14. module3=dso_literal
  15. module4=dso_section
  16. [dso_section]
  17. path=/some/path/to/some/dso.so
  18. other_stuff=other_value
  19. ----
  20. When this file is loaded a configuration module with the specified string
  21. (module* in the above example) is looked up and its init function called as:
  22. int conf_init_func(CONF_IMODULE *md, CONF *cnf);
  23. The function can then take whatever action is appropriate, for example further
  24. lookups based on the value. Multiple instances of the same config module can be
  25. loaded.
  26. When the application closes down the modules are cleaned up by calling an
  27. optional finish function:
  28. void conf_finish_func(CONF_IMODULE *md);
  29. The finish functions are called in reverse order: that is the last module
  30. loaded is the first one cleaned up.
  31. If no module exists with a given name then an attempt is made to load a DSO
  32. with the supplied name. This might mean that "module3" attempts to load a DSO
  33. called libmodule3.so or module3.dll for example. An explicit DSO name can be
  34. given by including a separate section as in the module4 example above.
  35. The DSO is expected to at least contain an initialization function:
  36. int OPENSSL_init(CONF_IMODULE *md, CONF *cnf);
  37. and may also include a finish function:
  38. void OPENSSL_finish(CONF_IMODULE *md);
  39. Static modules can also be added using,
  40. int CONF_module_add(char *name, dso_mod_init_func *ifunc, dso_mod_finish_func
  41. *ffunc);
  42. where "name" is the name in the configuration file this function corresponds
  43. to.
  44. A set of builtin modules (currently only an ASN1 non functional test module)
  45. can be added by calling OPENSSL_load_builtin_modules().
  46. The function OPENSSL_config() is intended as a simple configuration function
  47. that any application can call to perform various default configuration tasks.
  48. It uses the file openssl.cnf in the usual locations.