Skip to content
  1. Dec 20, 2003
  2. Dec 11, 2003
  3. Dec 10, 2003
  4. Dec 03, 2003
  5. Dec 01, 2003
  6. Nov 29, 2003
  7. Nov 28, 2003
  8. Nov 27, 2003
    • Richard Levitte's avatar
      If dynamically-loadable ENGINEs are linked against a shared-library version · 04dc4edb
      Richard Levitte authored
      of libcrypto, then it is possible that when they are loaded they will share
      the same static data as the loading application/library. This means it will
      be too late to set memory/ERR/ex_data/[etc] callbacks, but entirely
      unnecessary to try.
      
      This change (and a great part of this comment) was implemented in
      0.9.8-dev a long time ago, but slightly differently.  In 0.9.8-dev, a
      specific function that just returns a pointer to some static object is
      used. For 0.9.7x, we couldn't do that, since the way we handle feature
      freezes is, among other, to not add any more non-static functions.
      Instead, we use the function ERR_get_implementation() and compare the
      returned value with fns->err_fns, a member of fns that already is
      there, and which therefore can safely be used in this manner.
      
      What happens is that if the loaded ENGINE's return value from this
      function matches the loading application/library's return value - they
      share static data. If they don't match, the loaded ENGINE has its own
      copy of libcrypto's static data and so the callbacks need to be set.
      04dc4edb
  9. Nov 24, 2003
  10. Nov 22, 2003
  11. Nov 20, 2003
  12. Nov 19, 2003
  13. Nov 18, 2003
  14. Nov 16, 2003
  15. Nov 10, 2003
  16. Oct 29, 2003
  17. Oct 15, 2003
  18. Oct 11, 2003
  19. Oct 10, 2003
  20. Oct 07, 2003
  21. Oct 02, 2003
  22. Oct 01, 2003
  23. Sep 30, 2003